These pull back the field short codes and the fields entered/selected value, however has anyone found a way to get the actual field name?
The URL does not look correct, at least it does not work for me.
I did get it to work, thanks.However, the challenges are:It returns all fields on the form Navigating through Web Groups Getting the fields name from this REST call and matching it to the value in the field on a specific event
The attached is an approach I have used to base the visibility of one field based on the values selected in multiple custom fields. It is a workaround ‘for now’ for the issue of not being able to use logic in visibility expressions in the customizer.
Please log the idea, but you could possibly use ETM to retrieve all your Services and then the Offerings within each service, sort them alphabetically in your mapper, then using a subsequent mapper, update the sort order on the Offering to reflect the new order.I haven’t done this, but seems feasible. If it is a one time update, you could use the DMW to create a worksheet where you could update the sort order on the offerings and re-import.
Oddly, I don’t believe a task expression can return the time portion. However, assystREST and ETM will return the time portion. It’s not pretty, but you could add a task in the workflow to trigger an ETM channel that will grab the requisite date and time from those fields and then update a string field on the parent event that you can then reference in future tasks.I think this should be raised as an ide to be able to access the time component of the system fields.
Since you will only have a single stage created after the Approval, you can use an AP rule to trigger SmartMail based on that stage action on the parent event. The sample rule below could be extended if needed to only send on certain workflows or offerings. { [[ Send Mail to affected user Decision Approval Received ]], [[ (EVENT_TYPE == "r" or EVENT_TYPE == "s") and ACT_TYPE_SC == "POST APPROVAL STAGE SC" ]], strSendMailV2 .. "TEMPLATE=SM_INTERNAL_APPROVAL_RECEIVED RECIPIENTS=TO_AFFECTED", "continue" },
The CONTACT USER lookup is a ‘system’ lookup based on the contact user table (the usr table in the DB). That is why you don’t see it in the Custom Lookups in the customizer.Since the field does not have a filter on it, I am assuming that a user is only seeing users from their business area based on the user’s CSG restrictions. This makes sense if you have users segregated by CSG based on their origanization.If you don’t have CSGs activated on location or organization records, then you will need to use a system lookup based on the entity you are trying to search. For example, if your department is a ‘section’ record in assyst, you would use the ‘SECTION’ as the system lookup and apply a filter based on the affected user’s section, something like:select section.id from sectn as section where section.shortCode=@*@$new.affectedUser.department.section.shortCode@*@The additional system fields were introduced in 11.5.https://wiki.axiossystems.com/assyst11-5Wiki/index.php/Overview_of_the_Use_o
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.
