1. How do I retrieve the IDs of the attributes required to use the different actions in the connector (e.g., project, service, category, group, specialist)?

IDs can be retrieved in many ways:

• With Aranda Query Manager, you can create a report that queries the Aranda Service Management Suite (ASMS) table where the required data is located. If you need guidance on the data objects in the solution, please visit the link below https://docs.arandasoft.com/docs/database.html and identify the version of the Aranda database corresponding to your ASMS installation.
• If you are using an ASMS On Premise installation, you can query the ASMS table where the required data is located through a SQL client.
• Through the Aranda Support Center, generating a support request through the contact channels indicated on the following website Support.

2. What is the maximum size of files that can be attached when using the “Add Attachment” action?

The maximum size depends on the specific configuration of your ASMS instance/installation. Please ask your ASMS administrator.

3. What is the level of data access required by the technician account whose token is used in the configuration of the ASMS connection required by the connector?

The access level is the same as the technician account that is used in ASMS on a regular basis. That is, depending on the roles and permissions of the corresponding technician in ASMS, the data can be accessed with the connector.

4. Does the technician’s account whose token will be used in the connector need to be named or simultaneous?

Considering that the connector accesses the related ASMS instance multiple times per hour, it is recommended that the account be of the Named type.

5. Does the creation or modification of cases using the connector follow the same data validation rules present in the ASMS interface?

Yes, it follows the same validation rules. For example, when creating a case for a specific project, service, and category, if native and additional fields need to be completed, this data is also required when submitting the case through the connector.

6. Can the connector be used for ASMS instances in cloud and on-premises environments?

Yes, it can be used in both cloud and ASMS installations. On-premises, you should consider the connectivity between the ASMS server and your Power Automate environment.

7. I have a Power Automate license that only allows me to use standard connectors. Can I use the ASMS connector?

It is not possible, the ASMS connector is Premium type.

8. I want to create flows in Power Automate that start from events in ASMS (for example, when a case is created, when a case is assigned to a specific group). Is it possible to use triggers that start from events that occur in ASMS?

Yes, it is possible. The following steps are recommended:

• Initialize a “When an HTTP request is received” trigger and create a JSON schema of the request body that contains the data structure that is expected to be received from ASMS. Once the trigger is created, you will get an HTTP POST URL (URL WebHook) to use in your ASMS instance. Don’t forget to consider the authentication mechanism for accessing the WebHook URL (e.g., Token).
• Create a business rule in ASMS for the set of conditions that, when met, should initiate the flow in Power Automate. As an action within the rule, select “Invoke Webhook” and in the destination URL of the invocation, enter the URL of the previously obtained WebHook, the parameters to be sent, and the body of the request (which must match the JSON schema of the request body). For more information on how to invoke a Webhook from a rule in ASMS, visit the following link: Webhook Rule
• Test the created rule and validate that an HTTP request is sent to the WebHook URL and initialize the flow in Power Automate.

9. Can I invoke ASMS REST API endpoints as actions from flows in Power Automate?

Yes, it is possible. Use the “HTTP” action and fill in the required data (URI, Method, Headers, Body, among others).