Sunday, April 5, 2015

TBE: CSS fix for login area in CWS

 

Ok, a little expansion first. This is a CSS fix for the login area of the Career Website using Taleo Business Edition (TBE). The Careers Web Site (CWS), is Taleo's portal to get job-searching candidates to register and enter their information. TBE provides options to set up multiple CWS pages for different job types, but they will all inherit styles from TBE's cloud service. The login area is one such place in the page which cannot be customized. Due to an existing product defect, the text in the login area is misplaced and misaligned.

cleartext.blogspot.com

Eg: this is from one of many TBE CareerSites.

tmp25F8

Some other examples:

tmp3738

tmpA26A

tmp3A94

 

tmp739F

tmp3BEF

 

and so on…..cleartext.blogspot.com

Do you see the pattern ? In all of these sites, the text "Re-type new password" appears misaligned. The placement of this text cannot be controlled from within TBE, the login id and password fields are always together.  This is because this form layout is downloaded from TBE's public web servers, like most cloud applications, and thus the layout will be similar for any TBE user. Only minor UI enhancements like font type and size is inherited from the base parent website.

Now for the fix:

This simple form issue can be fixed with a minor CSS tweak into the CWS header itself. Just insert the following into the header enclosed inside text/css sections:

tmp376D

Save the header and try the CWS again, you should see the login area move into place something like this:

tmpD63D

Now the labels all appear in alignment on the left side, and the gap above the third field is removed.

To see a complete Career Web Site designed by me, see here.

 

 

 

 

This article first appeared on cleartext.blogspot.com

Saturday, April 4, 2015

BIP Logs

 

A quick roundup on how to set up the log levels on a BIP setup.

On the BIP Desktop Addon:

Here is how to increase Log levels on your windows machine, running the BIP Destop addon

cleartext.blogspot.com

1.Find out the Java folder your Word add on is using.
In side your Word's Addin Tab, go to BIPublisher -> Tools -> Options -> Preview

tmp2EF8

2. In this java folder, go to /lib/ folder, and create a file named xdodebug.cfg

3. Add these two lines the xdodebug.cfg file:

LogLevel=STATEMENT
LogDir=C:\xdo_logs

4.Create a folder named xdo_logs under C:\  Next time you preview a report on your addon, BIP will create logs in the folder.

This article first appeared on cleartext.blogspot.com

Alternate: TemplateViewer

If you want a quick method to get logs without making these changes, you could simply use the TemplateViewer jar file. It will be under the TemplateViewer folder under the BIP addon installation. For me, it was under :

C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\TemplateViewer\tmplviewer.jar

1: Just run the jar file in Windows.

tmp841B

 

2:Use the browse button to go a folder where you have your RTF template & XML data file.

3:In the left pane, select the XML file, and in the right pane, select the RTF file you need to test.

tmpACC2

4. Before you run the report, go to the Settings tab, and select log leve as Maximum.

tmp8B31

5. Click on the Start Processing button, to see the logs getting generated and the preview being generated.

On a BIP Server:

Here are the steps to change your BI Publisher Enterprise Server to be in a debug mode:

  1. Login to BIP as Administrator
  2. Select Admin -> System Maintenance -> Server Configuration
  3. Change Debug Level to ‘Debug’ under General Properties
    clip_image001
  4. Click on the ‘Apply’ button and restart the server.

 

When set to maximum log level, BIP will generate the logs, and in addition, create a .xml file, .xsl file, and a .fo file. The XML file will contain the dataset used to generate the report. The .fo file contains the final output, and can be renamed to PDF or whatever output you had chosen and it will open up in its viewer.

 

Happy BIP ! and Happy Easter !

This article first appeared on cleartext.blogspot.com

 

This article first appeared on cleartext.blogspot.com