Difference between revisions of "Help:Sandbox"

From SDU
Jump to: navigation, search
m
Line 1: Line 1:
−
Feel free to try out the wiki syntax in this page.<br>
+
'''
−
<!-- test your skills below this line -->
+
Format Properties Data Value'''
−
[[Test]]
+
−
[[Media:test.zip|Test zip file]]<br>
+
−
[[Media:filename.txt|File description]]
+
−
[[CA Workflow]]
+
  
−
<pre>
+
Please note that you will need to clear your web browser cache.  Also, would suggest you to review the Notes section at the bottom of this document to fully understand the limitations associated with this customization including the fact that this is a not supported customization
  
−
This is an example of the workflow to obtain the group members from Servicedesk.
+
'''Steps to activate the script file'''
 +
'''Download sitemods File :''' [[Media:sitemods.zip]]
  
−
Two workflows required are: 
+
1. Copy the sitemods.js file from $NX_ROOT/bopcfg/www/wwwroot/scripts to $NX_ROOT/site/mods/www/wwwroot/scripts
  
−
1. Import call_get_group_info as a standard process definition
+
2. Append the contents of the file sitemods.txt to the end of sitemods.js
−
2. Import get_group_info as standard process defintion, then add as a process actor
+
  
 +
3. Clear your web browser cache
  
−
Call get_group_info  - This is the process that calls the get_groups_info actor.  It passes two variables to the
+
4. Open the Request Area, Change Order Category or Issue Category “Property Template Detail” form for any properties that you want to provide a selectable list of values (on the web interface)
−
                                    Get_groups_info WF:
+
 
   
 
   
−
                    a. GrpAttributes - array of string containing the requested attributes
+
5. In the “Examples” field (“sample” attribute) enter following details to populate the corresponding html data control.  
−
                    b. GroupName - Group name (Name not UUID) of the group to retireve members from.
+
  
−
                    The GroupName variable can be set in the node labeled "Set Configurable Variables here"
+
'''View Sample :''' [[Image:Example.jpg]]
  
 +
6. Once you save this information by clicking “Save”, your control will be active for any new Requests/Incidents/Problems that use the Area
  
−
get_group_info      -  This is the actor which does the USD logon and retrieves the information. 
+
7. Similarly in the customer or employee interface if a property is defined with custom sample argument the control will be visible accordingly.
−
                                    It will generate an XML listing of the Members of whichever group is passed.
+
  
 +
'''Notes'''
  
−
The end result of the call_get_group_info WF will be two final variables containing comma delimted strings from the XML string and creates 2 comma delimted strings:
+
1. No SUPPORT for this CUSTOMIZATION:
−
$strUserNameFirstLastCSV contains Firstname.Lastname
+
This customization creates a new version of the following two (2) JavaScript functions:
−
$strUserIdCSV contains userid
+
• function detailWriteProperty() JavaScript function from the detail_form.js file.
 +
• CategorySink.prototype.showProperties = function() JavaScript code from the cst_cat.js file.
 +
• If these functions ever be updated in a patch, the changes will not take effect unless someone goes and ports the changes manually. This will be user’s responsibility. 
  
−
1) This two output strings can be used as a drop down for member selection in a form.
+
2. LIMITATIONS – Interface:
−
2) The loop can have another activity node that sends email to all users in the string, or whatever else you want to do with each element it finds in the string.
+
This functionality is not designed for and does not work on the Java-based USD Client. It is only designed to work in the Web Interface of USD r11.2.
  
−
<\pre>
+
Currently this functionality is limited to no of properties. It supports the property list up to 50.
 +
 
 +
3. LIMITATIONS – Updating Properties settings:
 +
Any administrative changes that are made to the Properties after the Request Area has been attached to the Request will not take effect on existing requests unless the Request Area is removed and reattached.  The same is true for Incidents, Problems, Change Orders and Issues respectively.
 +
 
 +
'''Testing'''
 +
 
 +
1. Tested and works with Internet Explorer
 +
2. It’s not tested to work on earlier versions than r11.2 of USD.
 +
 
 +
 
 +
----
 +
<div align='center'><font color="red">To make corrections or additions to this article, select the ''edit'' tab above.<br>
 +
To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>

Revision as of 14:27, 31 March 2008

Format Properties Data Value

Please note that you will need to clear your web browser cache. Also, would suggest you to review the Notes section at the bottom of this document to fully understand the limitations associated with this customization including the fact that this is a not supported customization

Steps to activate the script file Download sitemods File : Media:sitemods.zip

1. Copy the sitemods.js file from $NX_ROOT/bopcfg/www/wwwroot/scripts to $NX_ROOT/site/mods/www/wwwroot/scripts

2. Append the contents of the file sitemods.txt to the end of sitemods.js

3. Clear your web browser cache

4. Open the Request Area, Change Order Category or Issue Category “Property Template Detail” form for any properties that you want to provide a selectable list of values (on the web interface)

5. In the “Examples” field (“sample” attribute) enter following details to populate the corresponding html data control.

View Sample : Example.jpg

6. Once you save this information by clicking “Save”, your control will be active for any new Requests/Incidents/Problems that use the Area

7. Similarly in the customer or employee interface if a property is defined with custom sample argument the control will be visible accordingly.

Notes

1. No SUPPORT for this CUSTOMIZATION: This customization creates a new version of the following two (2) JavaScript functions: • function detailWriteProperty() JavaScript function from the detail_form.js file. • CategorySink.prototype.showProperties = function() JavaScript code from the cst_cat.js file. • If these functions ever be updated in a patch, the changes will not take effect unless someone goes and ports the changes manually. This will be user’s responsibility.

2. LIMITATIONS – Interface: This functionality is not designed for and does not work on the Java-based USD Client. It is only designed to work in the Web Interface of USD r11.2.

Currently this functionality is limited to no of properties. It supports the property list up to 50.

3. LIMITATIONS – Updating Properties settings: Any administrative changes that are made to the Properties after the Request Area has been attached to the Request will not take effect on existing requests unless the Request Area is removed and reattached. The same is true for Incidents, Problems, Change Orders and Issues respectively.

Testing

1. Tested and works with Internet Explorer 2. It’s not tested to work on earlier versions than r11.2 of USD.


To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.
Retrieved from "http://greggsmith.net/wiki/index.php?title=Help:Sandbox&oldid=1787"