nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Assign person custom field with a person

tchenm1

During a workflow progression I would like to set a custom type persons field to different people.

The "sop:sourceSubPerson" is our custom field associated to the parent folder of the document. However this line of code is not working.

parentFolder.properties["sop:sourceSubPerson"] = people.getPerson("Bautista");

Any input would be appreciated.

Find more posts tagged with

Comments

afaust

Hello,

please keep in mind that any changes to properties in a JavaScript-based action / script will only be saved when you explicitly call the save() method on the ScriptNode.

In your case:
<blockcode>
parentFolder.properties["sop:sourceSubPerson"] = people.getPerson("Bautista");
parentFolder.save();
</blockcode>

Regards
Axel

tchenm1

Hi AFaust,

Yes, I did call a save method just didn't include it in the code sample. I think the problem with the custom field (sop:sourceSubPerson) is that it is an association to the cm

erson class. When I view the node, I see that the sop:sourceSubPerson property contains the name. However, it does not appear in the Share interface.

When I populate the field through the share interface and view the node, the Association of the node is populated with the person target reference. So am I to assume I need to be saving an association? And how would I do that?

Thanks so much!!

Mike T

tchenm1

After surfing the forums below was the solution I emulated, hope it helps others. My custom field sop:sourceSubPerson was an association to cm

erson so an update to properties method did not do anything. An association must be created in the node containing the custom field and that was done by the below.

var parentFolder = document.parentAssocs["cm:contains"][0];
var person = people.getPerson('Bautista');
parentFolder.createAssociation(person, "sop:sourceSubPerson");
parentFolder.save();