- Read Input - Input is read from the Action Payload
- Data - Input is kept in a variable called
property.msg - ReadInputPayload - equipment_id, problemType, inputPayload is fetched from the msg. Also, account, company and user is fetched from the msg headers.
- Token Fetch - An http call is prepared to fetch token from FSM.
- Request Reply - The call to get token is fired and response is received.
- Read Token - Token from the call is saved in the access_token propety of the message.
- Call to fetch existing tickets is prepared - A post call is prepared with access_token, X-Client-ID and X-Client-Version in the headers. Body of the message has the query - Fetch service call and equipment id from the existing list of service calls where equipment id is same as the equipment id from step 3
andequipment id exists in the service call's list of equipmentsandstatus code is not -4 or -1 (closed or cancelled)andproblem type is same as the incoming problem type. - Request Reply - Call is executed and response is received.
- Check Count - Count of such tickets is retreived from the response.
- If the count is 0, proceed with service call creation to step 11. If the count is more than 0, End (16).
- Call to fetch BP - Another call is prepared to fetch the Business Partner of the current Equipment.
- Request Reply - Call is fired and response received.
- Get BP - Business Partner information is added in the call to create a service ticket along with other details. Due Date time is updated as the next day.
- Final call to create service ticket - A call to FSM is prepared with all the details collected in the above steps.
- Request Reply - Call is fired and response received.
- End
This sample application contains an iFlow definition to create service calls in Field Service Management that can be used in Actions Modeler.
Please follow below steps to import the iFlows.
-
Navigate and Open Access_Token_FSM.iflw file.
-
Replace the placeholders with relevant values as explained below.
| Place Holder Name | Details | Example |
|---|---|---|
| <<FSM_ACCOUNT_NAME>> | FSM Account Name | |
| <<CORE_SYSTEM_HOST_URL>> | Core System Host URL | https://us.coresuite.com |
| <<FSM_USER>> | FSM Username | |
| <<FSM_PASSWORD>> | FSM Password |
- Navigate to iFlows/FSMServiceCallWithDynamicParams and create archive file (zip file ).
- Zip file internal file structure should look like as per below.
├── META-INF
│ ├── MANIFEST.MF
├── src
│ ├── main
│ │ ├── resources
│ │ │ ├── scenarioflows
│ │ │ │ ├── integrationflow
│ │ │ │ │ ├── Access_Token_FSM.iflw
│ │ │ ├── script
│ │ │ │ ├── GetId&Voltage.js
│ │ │ │ ├── checkCount.js
│ │ │ │ ├── getBP.js
│ │ │ │ ├── get_access_token.js
│ │ │ ├── parameters.prop
│ │ │ ├── parameters.propdef
└── .project- Launch the Cloud Platform Integration Cockpit and login with the respective credentials.
- Import the archive file, this should create an iFlow called "FSMServiceCallWithDynamicParams".
- Deploy the iFlow by clicking on the "Deploy" button.
- After successful deployment, navigate to "Operations View => Manage Integration Content".
- Select the iFlow by the name "FSMServiceCallWithDynamicParams".
- Copy the iFlow URL listed under "Endpoints" tab right side.
-1(Electrical)
-2(Mechanical)
-3(User Error)
-4(Third Party)
-5(Unknown)