You should be able to reach the selected answer for a task event via the following path: event -> parentStage -> tasks -> answer For example: {server url}/assystREST/v2/events/{task event id}?fields=parentStage.tasks.answer (There will only ever be one task in the “tasks” array of the “parentStage” since it is a decision stage.) Thanks Julian, that works perfectly. Got the selected answer and some of the details of the user who answered by using the following field pre-population and filtering: {server url}/assystREST/v2/events/{task event id}?[parentStage[tasks[answer[answer], answeredBy[servDept[shortCode]]]]]
https://wiki.axiossystems.com/assyst11-4Wiki/index.php/Integrations:assystETM_1.5_-_Data_Mapping#commonHi Mauro,We have some common JavaScript functions available to Datamapper authors as linked from the wiki above. The key one for this would be common.parseDate(dateString, dateFormat). It takes the date value from your input, along with the target format (As described in Java SimpleDateFormat) to return a Date value.In use, if we have a CSV file like:mon_start mon_end ... 01/01/2022 09:00:00 01/01/2022 17:30:00 ... Our Datamapper could have a field mapping to the “Mon Start” field for an SLA, with the following JavaScript expression:common.parseDate(inbound["mon_start"],'dd/MM/yyyy HH:mm:ss');Which would look like this in the UI (With “Debug” running to show the result from the above CSV file)Hope this helps!
Hi Steve,This would need to be a manual process of downloading the attachment and then using some method to upload the file to ETM as you are doing currently.This sounds like a good enhancement suggestion however, so I would recommend creating this as an Idea in the Community for a possible future release of ETM.
The TooManyRowsException is being hit due to the search criteria not resolving to a single Event in assyst. The Formatted Reference Range provided is empty, and so this is effectively attempting to bring back all Events in the system.If the search should be completely skipped if a certain condition is met, in this case the initEventListSrch bringing back 0 results, this should be in the “Skip Search When:” expression.It is worth noting that the search for the Record to Update field can only support returning 1 exact result, so if the initEventListSrch brings back multiple results, it will still hit the TooManyRowsException. In my above example, I skip the search if either the “To” Email Address doesn’t match a specific value or if the initEventListSrch list length is not exactly 1.Skip search when:var skipSearch = false;if (common.extractEmailAddress(headers['To']) != "automated@helpdesk.com") { skipSearch = true;} else if (variables.initEventListSrch.length != 1) { skipSearch =
Hi,It is possible to get the current record number being processed within a datamapper, by using the following:headers["currentrecord"]However, it is not possible to access the total number of records within the import, so this is something you would need to know if it is a static value or access from the import data itself.I would suggest creating an Idea to be able to access this information from within an assyst ETM datamapper.Kind regards,Stephen
Hi Manish,When mapping custom fields, ensure that these are below fields which identify the Record to Update (If updating an existing Service Request) or the Service Offering that is used to create the Service Request. This is used by ETM to determine the form to use, and so validate against Custom Fields on that form.If the Custom Field is mapped below these fields, and the short code is valid, then please raise an Incident with our Service Desk so we can investigate this further,On skipping fields based on other mappings, this can be done by setting the “No Value” drop down on the field to be skipped to “Skip” instead of “Use Null”. In the expression for this field, you can return a null value based on some logic (Presence of a value for another field) and this will then skip the current field.To access previous mapped data within the same mapper, you can use “outbound”. For example, to get the value mapped earlier for the Short Code field, you can use:outbound["shortCode"]For Custom
Hi Manish,When searching for events, the minimum criteria required are Event Type and Event Status. If any of these are missing, then the search will return 0 results.Above is an example variable assyst search which will return a list of open Incidents which are currently assigned to the provided user. In your datamapper, you could set up multiple searches for different event types. The possible values for Event Type (Taken from the assystREST resource schema) are:<xs:simpleType name="eventTypesEnum"><xs:restriction base="xs:string"><xs:enumeration value="INCIDENT"/><xs:enumeration value="CHANGE"/><xs:enumeration value="PROBLEM"/><xs:enumeration value="NORMALTASK"/><xs:enumeration value="DECISIONTASK"/><xs:enumeration value="AUTHORISATIONTASK"/><xs:enumeration value="SERVICEREQUEST"/><xs:enumeration value="ORDER"/></xs:restriction></xs:simpleType>Kind regards,Stephen
Hi Chris,If the goal is to update a Product Version based on a provided Item, the Item itself will contain the Product Version id value if it has one.The following example uses a Variable assyst search to fetch the Item details using a short code value coming from inbound, and then the result of that in the Record to Update search for Product Version. Variable assyst searches always return a list, even if the search finds a single result, which is why variables.sourceItem[0] is used to refer to the first element in the list. Kind regards,Stephen
Hi,It is not currently possible to directly search for an Item by a custom field value via assystREST, and therefore within an ETM datamapper.I would suggest raising this an Idea for the assyst Product, specifically for assystREST and assystIPaaS/ETM.As a workaround, if you could also store the asset tag value in a searchable field, such as one of the User Field Chars (1-10), this would be directly searchable within the ETM Datamapper.Kind regards,Stephen
When any error message is hit or thrown within a JavaScript expression, the full exception message will be displayed. In the particular case of a search not bringing back an exact match, you can change the “No Match” behaviour to “Error”. This will cause the record to fail if all of the searches specified for this field return no exact matches. You can also fine tune it for specific searches with the “Error if No Exact Match” checkbox:With one of these enabled, the generated error message will be more concise. If the first method is used: If the more fine grained option is used, you will get the values it failed on:There currently isn’t a way to get custom messages (Aside from throwing an exception with a custom message) into the generated feedback email. You can have custom logging which will be added to the generated import log that can be downloaded from the UI using the following in your JavaScript expressions: logger.warn("This is a warning message");logger.debug("This is a debug
It is possible to retrieve a Query Profile by ID using the mechanism you have tried, it may be that the IPaaS service user does not have the privileges required to view Query Profiles or that particular Query Profile.However, it is currently not possible using an ETM assyst Request Datamapper (In your example above) to update the query parameters for a Query Profile. It may be possible to use a HTTP (assyst) Request Datamapper that was introduced in ETM 1.7 to make a custom assystREST request.https://wiki.axiossystems.com/assyst11-7Wiki/index.php/Integrations:assystETM_1.7_-_HTTP_(assyst)_Request_Mappers
Are you seeing this when you have queried for the Building in a Datamapper via a Record to Update or Variable assyst search, or prepopulation using the Data Management Worksheets?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
