How to create dynamic ID for document upload in DMS case ( Primary Key 1, Primary Key 2, and Primary Key3)
@DebugHorror There is no task as such you have to create an API for this and save the data and paste that data onto that field
Thanks @Ritikmehta for the answer.
This means I will have to create one API that will generate the Random ID or Number.
Seems like too much of task to just generate a random number.
@vipin.verma @naks @lmehta This could be raised as feature request.
Raised as a feature request here New Task to create Random Numbers/ String / UUID in vFlow
@DebugHorror - I agree this seems to be too costly operations if we have to use the API.
Thanks for raising the concern. We will check internally on the possible solutions.
Thanks and Welcome to community Nakul!
Let discuss this new feature here:
New Task to create Random Numbers/ String / UUID in vFlow
Created on DBES API with simple postgres query
SELECT uuid_generate_v4() as pk1, uuid_generate_v1() as pk2, uuid_generate_v1() as pk3 ;
It will return pk1, pk2 and pk3.
Just remember you first need to enable uuid-ossp
extension at database level by executing following command
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";
Ugly but will do the job.
@DebugHorror As a temporary solution you can also use this-
Create a control copy task in TaskGroup, and then in configuration section you have to select type as RANDOM, and leave blank copy from section and in Copy to you have give some any random path, which you can use in primary key 1,2,3 in the media uploader.
Note- A 6 digit Random Number is copied in the copy to path.
Yes, this could be the one solution but it will create keys which are more likely to get reproduced and may give primary key duplicate constraint.