Sequences
To manage the sequences on the platform, you must go to the Configuration menu and click on Sequences. This section of the platform configuration allows you to manage your sequences.
Sequences is restricted by specific roles. If you do not have access to this part of the platform and need to manage sequences configurations, please contact your administrator
Sequence list
The sequences are separated between Custom IDs and File Naming. The functionality remains the same with the difference between the two components being the generation of custom IDs for either outbound transactions or outbound files.
The sequences, Custom IDs, or File Naming, are not setup under this configuration tab. The sequences are utilized to only Reset or Set a new value.
Custom ID
Custom IDs are used for each payment transaction. The configuration is created under Channel.
File Naming
File Naming is used for outbound files. Each file can be configured to use a unique custom ID and is configured under Output Connectivity.
External Provider
In the Sequences list screen, you can:
-
Filter the list to view a more restricted list of sequences or perform a search or for External Providers filter by a range of dates and external providers.
-
Reload the table content by clicking on the Refresh button.
By selecting a specific sequence from the list, you can:
-
Display the entire history of the selected sequence. All changes made to the sequence since its creation are listed with the corresponding dates and the identity of the modifier.
-
Edit the information of the selected sequences to reset.
Sequence edit
-
The incremental value for SEQ is 5.
-
Enter a new sequence value for SEQ.
-
Click on edit sequence to apply the new value.
The outbound file has been generated with the new sequence.
Sequences dependency
Sequences are dependent upon custom File ID created under Channel or Output Connectivity for Custom ID and File Naming respectively. The customer ID needs to be created under SEQ or DAILYSEQ.
All outbound payments using this assigned channel would have their respective custom ID built on the above logic.
HeaderID: F20{SEQ:1:3}{DAILYSEQ:2:01}{DATE:%Y-%m-%d}
Result: F2000112023-11-17
Each transaction will have an incremental value where applicable.