Browsing Solutions For FCSUPPORT

  • Outlook security settings for EEO

    When using EEO in both classic client and in fcClient, Outlook client may prompt users if it is OK for another program to interact with Outlook. Example prompt: A program is trying to send email - do you want to allow this? Another prompt when using Execute method in the Outlook object model: Excerpt from msdn on the Execute method: When you run a program that uses the Microsoft Outlook object model to call the Execute method, you receive a warning message. This warning message tells you that a program is trying to execute an action or verb on your behalf and asks if you want to allow that. The warning message contains both a Yes and a No button. However, the Yes button is not available until five seconds have passed since the warning message appeared. You can dismiss the warning message immediately if you click No.

  • System running low on virtual memory.

    An application using fc APIs may runs low on virtual memory.

  • Biz rule message to include a URL screen pop

    http:// <Path to fcclient>/console/console.asp?command=casebyid¶m1=[Object ID] where <path to fcclient> will be something like myserver/fcclient Available Commands: newcase - No params required. casebyobjid casebyid crbyid prheaderbyid prdetailbyid newcaseforcontact - Requires two params: contact objid and site objid. contactbyobjid newinteract - No params required. Example: RE: Test Notification Something just happened on [Object Type] [Object ID] Click the link below to view this [Object Type]: http://localhost/fcclient/console/console.asp?command=casebyid¶m1=[Object ID]

  • Checkbox label click the checkbox

    1. Use the "for" property of the label control Example: <input type=radio name="product_type" id=by_site value="site_part" checked> <label for=by_site><b>Site Configuration</b></label> <input type=radio name="product_type" id=by_part value="part_num"> <label for=by_part><b>Part List</b></label>

  • Finding the line number of a server-side error

    Often, while developing, you will run into a server-side error that you wish to debug. Most of the fcClient pages have a try/catch around the entire page, and if an error occurs, it clears the page and shows a nicely formatted error message. However, it doesnt show the line number (as you typically dont want to show line numbers to end users). To get this information, simply comment out the try statement and the catch block on the page. For example, a page may look like the following: <% try { //code goes here %> html goes here <% } catch(e) { PrintError(e); } %> To see the line number, simply comment out the try and catch, as such: <% //try { //code goes here %> html goes here <% //} catch(e) { // PrintError(e); //} %>

  • Display localized time

    Example code: <% if (!bFindCaller){ var now = FCSession.GetCurrentDate(); var cust_tz = boTZ('full_name'); var cust_tz_name = boTZ('name'); var session_tz = FCSession.LocalTimeZone; var cust_time = FCSession.ConvertDate(now,session_tz,cust_tz); var cust_time = formatDate(new Date(cust_time),"M/d/yy h:mm:ss a"); rw('<b>Current Customer Time: <input type="text" name="cust_time" value="' + cust_time + '" style="width:140" disabled>'); rw('<input type="text" name="time_zone" value="' + cust_tz_name + '" style="width:75" disabled>'); } %>

  • Display the age in the console

    Here's an example of displaying "age" in the console. However, like the Clarify Classic client, this would display how long the case has been in the wipbin or the queue, not how long its been since the case has been created. <% //Display age in wipbin or queue var age = boCaseView('age'); var curr_time = FCSession.GetCurrentDate(); var diff = DateDiff(curr_time, age); var sec = FormatSeconds(diff); Response.Write('<td nowrap onclick="this.parentElement.children(0).click();">' + sec + '</td>'); %> This is only an example! For one, I would move the call to GetCurrentDate to the top of the page - there's no reason to make this database roundtrip for every row in the wipbin or queue. If you want to show how long the case has been opened, then I would add the case.creation_time to the appropriate wipelm* and queelm* views, and then use that fields to calculate the elapsed time.

  • Code which runs after a date/time has been picked from the calendar control

    Add a hidden element with an id of cal_callback, and have this element's click handler do the code you want. <input type="hidden" id="cal_callback" onclick="fcn_cal_callback()" value="cal_callback"> function fcn_cal_callback(){ //calendar callback function alert('a datetime was just picked'); }

  • Add help to a page

    1. Create a new help page, such as site_help.htm 2. Place this new file in the same directory as the page you want to post it form, i.e. /pages/site/ 3. In the calling page, add the following (setting the value to whatever you want your help page to be): <input type="hidden" name="help_page" value="site_help.htm"> 4. Be sure your calling page includes client_utility.js 5. Test: Post your page, such as site.asp, and press F1. Your custom page should show, and the default IE help should not.

  • Coloring the selected row in a grid

    1. Make sure you're including client_utility.js: <script language="javascript" src="../code/client_utility.js"></script> 2. Make sure your table has an id attribute: <table id="prev_cases_table" > 3. Define a module variable to hold the index of the previously selected row <script language="javascript"> //Module variable for the previous selected grid row var prev_grid_sel_row = -1; </script> 4. Add the following to your <tr> element: - defColor attribute; This is the default color for your row - bgColor attribute; This is the row's starting color - id - onClick handler that calls GridRowClickHandler. GridRowClickHandler takes 3 parameters: - this (doesn't change) - id of the table - module name of variable that contains the index of the previous selected row in the table (we need to pass this in, in case we have multiple grids on one page) Example: <tr class="clsGrid" defColor="" bgColor="" id="grid_row" onclick="GridRowClickHandler(this,'prev_cases_table','prev_grid_sel_row')" >

  • Save, Discard, Cancel not available on workflow actions

    If a Case, CR, PR Detail, etc. is modified in fcClient, and then a "workflow action" (discard, assign, move, etc.) is performed before the changes are saved, the modifications are lost (cleared). In Clarify, the modifications are not lost (cleared), the dirty bit remains set, and, after the "Workflow action" is completed, when "Done" is selected, the Save/Discard/Cancel prompt allows the user to decide if the changes will be saved or not. Scenario: Login to fcClient Open an existing Case Make some changes to the values on the form Now, Dispatch, Assign or Move the Case Result: The modifed values are reset to the original values, before the action was performed. Login to Clarify Open an existing Case Make some changes to the values on the form Now, Dispatch, Assign or Move the Case Result: The modifed values are retained after the action is performed. When you then press "Done", the Save/Discard/Cancel form is presented, and you can decide whether to keep the chnages or not..

  • Results appear differently between Clarify and fcClient

    You may run accross an issue where results appear to return differently in the Clarify Classic Client and fcClient for the same screen.