Skip to main content

Hello Community!

 

I am attempting to transfer engineering parts to inventory as part of a workflow. The process includes creating a record in the EngRevTransferHeadSet set of the EngineeringRevisionTransferHandling projection. When created through the UI, the record includes a non-null RecordSelection property. However, I cannot get the RecordSelection property filled with a value when created through the workflow. I’ve tried adding it in the Create action and through an Update action, and neither input has been accepted.

 

I tried hardcoding the record into the projection action, and the record still gets created with a null RecordSelection value. I tested with the following formats, none of which have worked:

  1. >“SITE=100^PART_NO=TEST-PART^ENG_REVISION=R01^”]
  2. /\”SITE=100^PART_NO=TEST-PART^ENG_REVISION=R01^\”]
  3. “\”SITE=100^PART_NO=TEST-PART^ENG_REVISION=R01^\”]”
  4. Saved attempt 1 as an ArrayList and used ${ArrayList.toString()}
  5. I tried using the invisible separator characters that are actually used in the attribute strings in the database, but the workflow would not deploy because the special characters 0x1e (Record Separator) and 0x1f (Unit Separator) are not supported by XML 1.0.

 

 

I also tried using an update action to update RecordSelection from null to the intended value, along with other updated values. The other values get updated but RecordSelection does not.

 

Because RecordSelection is null, the rest of the transfer process fails to do anything. There are no errors, but the parts don’t get transferred. Any suggestions on what I am doing wrong and how to fix or work around?

Hi Dylan.

I’ve seen this kind of issues with other type of fields such as multiselection attributes. Maybe this kind of attributes where information is encoded in the form of fKEY=VALUE^KEY=VALUE^KEY=VALUE] are not supported.

I’ve asked internally. I’ll let you know once I get the information.
Best regards.
Gonzalo.
 

Hi Dylan.

I’ve seen this kind of issues with other type of fields such as multiselection attributes. Maybe this kind of attributes where information is encoded in the form of fKEY=VALUE^KEY=VALUE^KEY=VALUE] are not supported.

I’ve asked internally. I’ll let you know once I get the information.
Best regards.
Gonzalo.
 

Thank you, Gonzalo. I’ll be interested in that response. In my understanding, workflows are meant to replace SQL Event Actions, but it seems that there may be many limitations to workflows that can be handled in event actions (such as creating an attribute string and directly calling the method).

Hi, 

I think in this case the RecordSelection attribute is of a type CLOB/LongText. Attributes in that type is not supported in workflows 

  • Blob, Clob, GIS, and File datatypes are supported only in cases where projections that manipulate them behind the scenes are called.

ref: Considerations Before Designing a Workflow - Technical Documentation For IFS Cloud

Hi Dylan.


Yes, workflows are meant to be replacing the Online SQL action but there are some limitations at the moment that need to be taken into account. As Kaminudu indicates, please have a look at the “Considerations Before Designing a Workflow” section in the documentation.


You might try to implement as a workflow but in case you hit a limitation you need to decide whether to go with a Online SQL event action or maybe do a regular modification.

Based on the information in API Explorer, the attributes description indicates the following:

 


RecordSelection is not a regular string, so it’s very likely that currently, the IFS API (previously known as IFS Projection) doesn’t support it.

Thank you much.
Best regards.
Gonzalo.​​​​​​​

Thank you both. We will consider changing the scope or creating a modification.

Reply


Terms & ConditionsCookie settings