- Tue Nov 06, 2012 6:28 am
#31040
Hi,
I've been thinking on a solution to reuse existing case data into a new case.
For this example we generally collect specifications and client information throughout the course of a process. Then wanting to reuse that data without re-entering would be an advantage, there would be only minimal changes to loaded case info, new dates, some other minor variation.
At this point I'd try to use a simple dynaform and a new task for the existing process that accepts the case number to clone then use a trigger to collect the JSON data from the workflow table and either
1: update the current case record in the workflow table with the data (overwriting any existing info)
2: manually trying to assign/parse the loaded case variables within the trigger to the current case
I think the first option would take less work and is likely to work, i think that most the other data about the case (dates/users/case history) are stored elsewhere and would just be blank while the case is routed throughout the rest of the process.
Any thoughts?
Cheers
I've been thinking on a solution to reuse existing case data into a new case.
For this example we generally collect specifications and client information throughout the course of a process. Then wanting to reuse that data without re-entering would be an advantage, there would be only minimal changes to loaded case info, new dates, some other minor variation.
At this point I'd try to use a simple dynaform and a new task for the existing process that accepts the case number to clone then use a trigger to collect the JSON data from the workflow table and either
1: update the current case record in the workflow table with the data (overwriting any existing info)
2: manually trying to assign/parse the loaded case variables within the trigger to the current case
I think the first option would take less work and is likely to work, i think that most the other data about the case (dates/users/case history) are stored elsewhere and would just be blank while the case is routed throughout the rest of the process.
Any thoughts?
Cheers