Question about Stibo Step

No responses

No responses

I think you are looking for something like this: if (context.proxy.isAssetReferencePartObject(unapproved)) { var refTypeId = String(context.proxy.getAssetReferencePartObjectReferenceTypeId(unapproved)); context.logger.trace("DAM: Unapproved reference type is: " + refTypeId);

I am sorry, but I am not sure I understand your suggestions. If you wish, we could continue this discussion here: https://www.reddit.com/r/Stibo/

Thanks for the answer. Yes, it is not possible without implementing a custom extension in OIEP.

Think hotfolder would equal Location_data , and in folder would equal in .

Think something like this probably works with the java api/business rules, but for the javascript business rules stibo is the main repository. So the external editor is just to help with editing, not keeping the whole repository / interlinking everything.

I believe, if you allow inherited usually in the stepxml export it will tag which ones are inherited and which ones are not.

I think so. Go to the User object. Look at the name pattern field.

No responses

Have not tried this specific component. But if your getting an error, than you can log a support ticket, and stibo should assist. At least that is my general experience.

That's actually not as straightforward as one would think. One idea would be to do a config export using stepxml and then search that for references to the attribute.

Have not tried the import method. Think it would have complications. Like what about all the passwords?

No responses

There are several options, I have done something similiar for a client in the past. 1. Remove unmapped in the advanced tab of the import configuration. However, here you will have to be careful when importing, as things will get implicitly deleted. Personally I don't like this approach. 2. STEPXML import with delete tags. more info you can find online in the help section. However, to get from excel to stepxml is not easy. 3. Use delete flags and a business action embedded in the import configuration. There is quite some setup involved but the result is a transparent and controlled process which is good. Create a new attribute 'Delete Flag' that is valid for the reference type and has validation base LOV for example. Make the LOV values 'Delete' and that's it. Now you have the ability to declare per import the references as marked for deletion by setting the value on the flag to Delete. You can pass this from excel by mapping a column and transforming the value, as you wish. Create a Business rule that looks for the value on the flag and deletes the reference if it has the right flag set. Save this as an import configuration and embed it in a widget or an IIEP. If you have questions , don't hesitate to contact me. Regards, Edo

You can do it using xml as well. First export the xml and then empty the values you dont need and import it back. Ofcourse Excel is much safer.

You can control attributes both by product type, see the validity tab on the attribute configuration. You can also control by product hierarchy see references tab on the attribute configuration (valid in products).

Yep, it is just a user permissions issue. If the users have the necessary permissions they will see 3 buttons for workflow. One with their tasks, one with their groups tasks, and one with all tasks. Then they can click on the one with all, and see the one for the team member that is out.

No responses

You can import via stepxml. Export some via stepxml. And you'll see the format.