Event Target Overrides

Nextworld Platform
1

Hello,

I have documented the following steps for event overrides after finding issues in prod environments while testing. Can someone please confirm these are the right steps? I am omitting the AWS values.

Go to environment override assignment setup application (may need to request access)

  1. Confirm there is a configuration for nsCoxSetSpecialOrderStatusEB (can change name is desired to something less specific)

  2. In Environment Override Definitions make sure you have the following event targets (Screenshot 1): nsCoxSetSpecialOrderStatusEB and nsCoxServiceOrderChangeEB

  3. Will need to make sure the right values are set for ID and role:

    1. Target: arn:aws:events:us-east-1****

    2. KEY arn:aws:iam::638222044552:role/awsxtime***

2

@ian.p maybe you can point someone to this post or answer please? This is time sensitive.

3

The steps you mention seem correct to me and align with what is written about this in Nextworld Help:

image
image3820×1471 309 KB

1 Like
4

@ellen.kaufman Yes, your documentation is correct. For external event targets, you are able to use the Environment Override tool to override 2 fields: ExternalEventTargetId and ExternalEventTargetRole. Once the overrides have been set up, in that environment those new values should be used at runtime for that specific event target, instead of the values stored within the event target record.

2 Likes
5

Sorry so here I say the environment override assignment application but you can only set these keys in Event Override Definitions. Do we have to set up the keys there instead?

6

@ian.p @alex.solorio

7

You need to use both apps in the following order:

  1. Environment Override Definitions: Define the fields and values you would like to override.
  2. Environment Override Assignment Setup: Indicate that for X environment, you would like to use Y Environment Override Definition (created in step 1)
2 Likes