Introduction
This feature allows to load the entity screens Work Orders, Assets, Positions, Systems and Parts with pre-filled fields by using parameters in the URL.
The format of the URL is as follows:
https://eamlight.cern.ch/<pageName>?<parameter1>=<value1>&<parameter2>=<value2>...&<parameterN>=<valueN>
Where:
- https://eamlight.cern.ch/ is the root URL to access the application
- <pageName> specifies the screen in the application. Possible values are:
- workorder
- asset
- position
- system
- part
- <parameterN> is the code of the parameter to be posted
- <valueN> is the value for the parameter.
Please note that the character "?" in the URL starts the part of the URL containing the parameters part, that each parameter/value pair is linked by the equal sign and that the character "&" separates the parameter/value pairs.
An example of a parametrized URL:
If the value contains spaces or one of the characters "?","=" or "&", they need to be encoded. Space is encoded as "%20"
The available parameters are listed below by entity.
Possible Parameters
Work Orders
| Parameter Code | Comments |
|---|---|
| description | Description of the Work Order |
| classcode | WO class |
| statuscode | Status code (e.g. R, RA,RDT) |
| typecode | WO type code (e.g. CD, EX) |
| departmentcode | Service unit code |
| equipmentcode | |
| locationcode | |
| prioritycode | e.g. L, M, H |
| reporteddate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| requestedstartdate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| requestedenddate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| schedulingstartdate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| schedulingenddate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| startdate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| completeddate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| problemcode | |
| failurecode | |
| causecode | |
| actioncode | |
| costcode | Valid CERN budget code |
| assignedby | |
| reportedby | Valid CERN ID |
| assignedto | Valid CERN ID |
| standardwo | Standard work order code |
Assets Positions Systems
| Parameter Code | Comment |
|---|---|
| description | |
| alias | Unique secondary code |
| classcode | |
| categorycode | |
| statuscode | Status code (e.g. I) |
| departmentcode | Service unit code |
| commissiondate | Format dd-MMM-yyyy. Example 25-MAY-2017 |
| assignedto | Valid CERN ID |
| criticality | |
| partcode | |
| manufacturercode | |
| model | |
| serialnumber | |
| hierachyassetcode | |
| hierarchypositioncode | |
| hierarchylocationcode |
Parts
| Parameter Code | Comments |
|---|---|
| description | |
| uom | Unit of measure code (e.g. pce) |
| classcode | |
| categorycode | |
| trackingmethod | |
| commoditycode | |
| trackbyasset | Possible values: "true", "false" |
| trackcores | Possible values: "true", "false" |
Additional parameters applicable for all screens
| Parameter Code | Comments |
|---|---|
| udfchar01 etc. | |
| udfdate01 etc. | Format dd-MMM-yyyy |
| udfnum01 etc. | |
| udfchkbox01 etc | Values can be "true" or "false" |
| <custom field code> | The classcode is required when adding custom fields |
An example of a URL with a custom field is:
https://eamlight.cern.ch/workorder?description=Test%20WorkOrder&classcode=RP01&0001=145950