Configuration
In the Configuration section, you have access to the Versions, Rules, Domains, Transaction Resp. Code and Business Parameters pages. In these pages, you have different actions that allow you to work on and edit the rules in different versions, activate the versions so that their rules have effect on the app, and see the parameters applied to the AS console operation, among other tasks. Refer to the table below to learn more about each page.
Versions are mechanisms that allow you to identify a specific configuration of rules - each version corresponds to a set of rules applied to an app. They allow you to configure and deploy rules in bulk, without affecting the system's stability. In addition, if you identify errors in production derived from the rules in the activated version, you can roll back to a previous version. In this page, you can create, edit or activate a version. | |
Rules are specifications that define parameters related to users, tokens, sessions and OTCs and define how users operate on the app. They allow you to define conditions for the creation, validation and authentication of users, their passwords and associated tokens. In this page, you can search the rules associated to a specific domain and version, organized under specific categories and subcategories and review their content. | |
Domains allow you to segment users according to their security profile and apply a set of rules for each segment. In this page, you can create or edit domains, and assign them to sets of rules. | |
Transaction response codes translate the responses given by the AS service into response codes for the transaction executed. In this page, you can search for transaction responses and see their details, and edit the messages that might be shown to users when the transaction is executed. | |
Business parameters are configuration sets that define the business environment you are working on. In this page, you can search for business parameters, see their details, and edit their values. |