Difference between revisions of "Object URL Syntax"
Ann Vincent (talk | contribs) m (→Usage Examples) |
Mark Bridger (talk | contribs) (→Overview) |
||
| Line 1: | Line 1: | ||
=Overview= | =Overview= | ||
| − | + | Designed for internal staff and partners, we’ve introduced a syntax that dynamically resolves URLs for various system objects and actions. This allows configuration teams to reference system objects using variables, streamlining setup when cloning new systems. Previously, configuration teams had to manually adjust URLs due to unique attributes like IDs which differ in cloned systems. Now, with this new syntax, links to assets such as login and signup pages, report charts, submit buttons, and portal sections will automatically point to the correct system asset after cloning without requiring manual intervention. | |
=Syntax= | =Syntax= | ||
Revision as of 11:15, 26 March 2025
Overview
Designed for internal staff and partners, we’ve introduced a syntax that dynamically resolves URLs for various system objects and actions. This allows configuration teams to reference system objects using variables, streamlining setup when cloning new systems. Previously, configuration teams had to manually adjust URLs due to unique attributes like IDs which differ in cloned systems. Now, with this new syntax, links to assets such as login and signup pages, report charts, submit buttons, and portal sections will automatically point to the correct system asset after cloning without requiring manual intervention.
Syntax
The general format of the syntax is the following:
@ssurl(objecttype,action,identifier)@
- The "identifier" parameter may consist of more than 1 object. Multiple objects can be separated by using double semicolons ( ;; ) as a delimiter.
- For some objects, the system enforces unique naming. For example, if you create an autoloader named "MyAutoloader", it is possible to create another autoloader also named "MyAutoloader". In these situations, we will simply return the object with lower ID.
Note: Configuration should avoid these scenarios to begin with.
Usage Examples
See table below:
| Description | objecttype
|
action
|
identifier
|
Examples with Resolved Results |
|---|---|---|---|---|
| Signup Page | signup | view |
Signup Page Name |
User Page Example:
/s_signup.jsp?token=XVtQC1oGZlBfRxddXxdSQUlSZ1R9Ew%3D%3D
/s_csignup.jsp?token=XVtQHUUGZV1YShBFQhdQXlZSZVxy
/s_csignup.jsptoken=XVtQHUUGbFxRQhFaXxdSQUlSZ1R9HQ%3D%3D&ptoken=XVtQC1oGZlBeQBNZXxdSQUlTYFZzEg%3D%3D
/s_csignup.jsp?token=XVtQHUUGbFxcRhRRXxdSQUlSZ1R9Eg%3D%3D |
|
UTA - Main List View |
uta | listview | UTA Name |
/iface/uta/uta_list.jsp?appid=102161 |
|
UTA - Create Level One |
uta | createlevelone | UTA Name |
/Apps/app_editopportunity.jsp?appid=102161 |
|
UTA - Template Page |
uta | templatepage |
UTA Name, Type Name |
/ex/ex_Apppage.jsp?token=HwwPRhMGZVla |
|
UTA - Impact Quadrant |
uta | impactquadrant |
UTA Name, Quadrant Name |
/Apps/db/db_impact.jsp?impactid=@Hw0ERBkfbV5bQRRQRh8~ |
| Report | report | view | Report Name |
/userreport/ur_openreport.jsp?reportid=44372 |
| Report Chart | reportchart | view |
Report Name, Chart Name |
Client-Side Chart Example:
/ex/ex_highchart.jsp?enc=1&chartid=H3ZfFAVpLgcxAVQ8GFAMERALMTY1QRYeH2JdUEJB &reportid=f1oJDE4bexInFm8TRRYqIxEmPA8rbTAKH2dZUkVG &rootcompany=GGZzFn0FZhk8JRocHGdIBBI7EzUSYAcDH2JcUg~~
/servlet/wChartwidth=300&height=200 &codedid=YnoRF35kEjwDHm0DMUQMNQ0kZwcdHTgRH2JdUEJC |
|
Report Dashboard |
dashboard | view |
Dashboard Name |
/userreport/ur_viewdb.jsp?dashbid=2348
|
|
SmartFolder (View) |
smartfolder | view |
SmartFolder Name |
/s_editresource.jsp?display=1&resourceid=68826 |
|
SmartFolder - View (Internet Enabled) |
smartfolder | viewinet | SmartFolder Name |
/files/113/68827/169542folderinet/ |
| Autoloader - Dropbox | autoloader | dropbox | Autoloader Name |
/Archive/al_upload.jsp?loader |
| AI Insight | aiinsight | view | Name |
/AI/ai_workingwithai.jsp?token=%40HwwMTxwbeFhFQhFFQRxZQVVTZFV1G3BhHQ~~ |
