Skip to main content
1-Visitor
December 14, 2015
Solved

ESI - How to prevent user from sending "non-latest" iterations to a distribution target?

  • December 14, 2015
  • 3 replies
  • 1961 views

Hi,

is there a preference or setting which prevents the user from sending a "non-latest" iteration to the distribution target?

Background:

With the "Send to distribution target" action we're pulling a number from SAP. If the user perfoms this task on a version which is not latest, the newer iterations won't get the number assigned.

Best answer by syadala

One way you can achieve this is with a action validator where you can validate the object and either display or hide the action. If you need any further assistance please mail me.

Regards

Sudhakar

3 replies

syadala12-AmethystAnswer
12-Amethyst
December 14, 2015

One way you can achieve this is with a action validator where you can validate the object and either display or hide the action. If you need any further assistance please mail me.

Regards

Sudhakar

1-Visitor
December 15, 2015

Thanks, this is a good point.

I'll check this with our programmer, but it might be easier to throw an ESI exception during the number assignment logic than creating an action validator. This would also be sufficient.

16-Pearl
July 20, 2016

Not sure if this would help.

remove Read access to ESIRelease for ESI Authors group (but not ESI Admin). Then add

Capture.JPG

for ESI Authors.

The ESI Closeloop witll hang at "Post Release" and then complete.

ESI does complete.