Just wanted to verify something in regards to automation and the build in beanshell. Example below:
OKMPropertyGroup.getInstance().setPropertySimple(null, uuid, "okg:IandT", "okp.IandT.link", http);
I have a script run when someones adds a document to a metadata group. This script puts in a html formatted string into one of the metadata fields (click the link to get to the associated ticket in jira).
I am using the variable uuid (injected directly, object unique identify , from documentation). When the script runs, is it setting the "uuid" string variable to the uuid of the document that was just added to the metadata? Whenever i run my script with uuid (via automation), it always overflows with bsh target exceptions. When i run the same code/script with a hardcoded document uuid, script has no issues. Am i using the uuid correctly? Or is there another way to get the uuid of the document that the automation beanshell script is working on? Thanks!
OKMPropertyGroup.getInstance().setPropertySimple(null, uuid, "okg:IandT", "okp.IandT.link", http);
I have a script run when someones adds a document to a metadata group. This script puts in a html formatted string into one of the metadata fields (click the link to get to the associated ticket in jira).
I am using the variable uuid (injected directly, object unique identify , from documentation). When the script runs, is it setting the "uuid" string variable to the uuid of the document that was just added to the metadata? Whenever i run my script with uuid (via automation), it always overflows with bsh target exceptions. When i run the same code/script with a hardcoded document uuid, script has no issues. Am i using the uuid correctly? Or is there another way to get the uuid of the document that the automation beanshell script is working on? Thanks!