3.1.16
New Features
1. Frontend Framework Upgrade
a. NodeJS version upgraded to v20.16.0
b. Which is used for generating build. No visible changes in Ul.
2. Amaya Feature Enhancement
a - Multi role support if application supports multiple role assignments.
b. Conditional Node with expression builder using forwarded data variables
c. Transformational node to modify existing data or add new attribute. (this is mostly used for sync operation)
d. API node (for create/update/delete/rdle assign/role unassign)-resolved one bug which was always required to call additional API to get UID
e. ITERATOR node(for sync operation) user's objects list can be transform and update/add fields.
f. -Subflow-This is the flow which will be applicable for iterator node
g-Run Flow (Debug/Implementation Purpose Feature)- this will execute the flow with mock data that can be filled by user ad execute to understand that whether flow is correct or not.
h-Run Request (Debug/Implementation Purpose Feature)- This will also ask the placed variables before execution, which will help the user/engineer to understand the behavior of flow, without using actual provisioning operation (without connector), but once integration completed, connector will be required for provisioning.
3. SSO Policy-12 hour frequency added for application MFA.
Bug fixes
Generator config-if config is disabled and rule is also created for that generator getting error
Recon Pull-AD-Sync action failed extor coming while executing the
Redis cache-Application tag reflected in device and vice a versa
APPfication MFA-Need to change label on detail
Amaya-In Condition node user is able to type variable but not able to create it
Amaya- When variables are marked in picker, they should be forwarded in condition node inside Iterator node, currently showing blank No option)
Amaya- Run flow Validation for the condition node should be added to prevent execution if the condition node is left empty and run flow is executed
Amaya- Pick properties should be visible inside API node, in variable environment
Amaya-Iterator node- When there is no connection between nodes and data is saved in the API node, both success and error validation messages are displayed simultaneously.
Amaya-Iterator node- Validation message is not displayed when the Save button is clicked
Policy Map-For the Start Date field, the Update button does not get enabled unless the Validate button is clicked.
Amaya- Client id should be visible in encrypted form
Application-Date time format is not supported
Amaya-User creation is failing even after retrying, despite correcting the create operation configuration
Amaya-Transformation node data overlaps when havering over the node
Amaya-After changing dropdown, condition value field should get empty/reset
Amaya-Berator Node- Showing error message on deleting iterator node
Amaya- Quick Setup- When any attribute is searched in the generate policy map, the other pages become unresponsive not able to edit
Amaya-Variabile are not getting forwarded into the second condition node
Amaya-Zoho Expenses roles- Cannot assign multiple roles in Zoho Expense, and there is also no option to remove a role once assignect, so showing application in failed state
Artaya- Recton pull having login generator configured-Login name is not visible after executing the recon pull from Amaya when a space is entered against login field of the transformation node
Admens-While logged in with "m32.Swettenham" user having org admin role, while login with that user admin module is not accessible
Logging in as an admin-the Admin tab is not loading and is directly landing on the Self-Service side
Known Bugs
manager notification: receiving user name required manager name
In application setting if show to user flag off then also application show in recent application.
Amaya || Unable to identify application properties data type where value is empty
Known || Amaya || Create user operation fails due to invalid password
Last updated
Was this helpful?