How to move data from clipboard in pre-prod(ITE) to prod environment ?
The requirement is - I have a WO in Pre-prod(ITE) environment, and I have case which has relevant data in clipboard. Now i want to move that clipboard data(specifically 2 pages) to prod WO. Any idea how to do that ?
Updated: 12 Sep 2022 6:34 EDT
Accenture
SG
Hi @YashM620,
I believe we don't have any way to move data of clipboard from one env to other but, one approach I can think of is write a onetime utility and set the necessary data.
- Open the case using handle
- Set the data that you wanted
- Save and commit
Thanks,
Vinay
Updated: 12 Sep 2022 11:28 EDT
CGI
IN
@VinayKumarL16594575 Hi Vinay, I believe u mean to set data using utility or activity in prod environment. Am i correct? If yes the only problem seems to me is there are too many properties.
Updated: 13 Sep 2022 1:00 EDT
Accenture
SG
Yeah running utility only. If you have too many properties then you can try the below two approaches.
- Open the work object in pre-prod(ITE) and use convertPagetoString and take the JSON. In the one time utility parse the same Json in PROD and copy the required pages.
- If you have only one or two WO then you can use package work wizard and move these 2 cases to prod and copy data from these 2 WO and delete them ( do this only if your team agrees to move the cases to prod )
Thanks,
Vinay
Bentego
TR
Hi @YashM620,
If you are willing to move entire work object, you may create product rule along with utilizing its "Class Instance to Include" capability like example below. CaseToBeMigrated RD is for filtering the work objects that you are willing to migrate to production. However, you need consider about assigning work object to respective work queue or operator on prod after migration done. Because, we only moved case instances not their associated assignments if any on pre-prod.
--
If you are willing to move particular page or page list (let's say items or spare parts entity of work object) belongs to work object in pre production. Well, you may serialize the page to JSON string with using function below then save it some location in drive.
then introduce activity with mandatory parameter let's say deserializeTextVal1, deserializeTextVal2 and etc. and deserialize their values to map some temp pages within activity through utilizing another function below.
Hi @YashM620,
If you are willing to move entire work object, you may create product rule along with utilizing its "Class Instance to Include" capability like example below. CaseToBeMigrated RD is for filtering the work objects that you are willing to migrate to production. However, you need consider about assigning work object to respective work queue or operator on prod after migration done. Because, we only moved case instances not their associated assignments if any on pre-prod.
--
If you are willing to move particular page or page list (let's say items or spare parts entity of work object) belongs to work object in pre production. Well, you may serialize the page to JSON string with using function below then save it some location in drive.
then introduce activity with mandatory parameter let's say deserializeTextVal1, deserializeTextVal2 and etc. and deserialize their values to map some temp pages within activity through utilizing another function below.
After that update work object(s) on production with opening and setting the related page(s) values with the page(s) you deserialized eventually save and commit the work object(s)
Let me know the result whether it works or not.
Regards.
Mert.
