Operation Settings

When no guidelines are given for the operation binding with the Override Settings check box selected and with the Allow all Operations check box selected, the guideline in the operations editor takes effect.

If transactions of same operation type are batched, the override settings for the particular operation binding take effect only when these transactions are transmitted for the interchanges with multiple groups of the same transaction type. In addition, these overrides cannot take effect when batch transmission is performed through a gateway.

To override outbound settings for a Notify operation, select the Override Settings check box. If you select to override settings, continue by configuring the following tabs:

General

The following options are available when overriding the settings:

Override Settings for Notify: General
Field Description
GS02 Sender/GS03 Receiver (for example, Application Sen: Application Rec)

Specify the GS02/GS03 values for outbound and inbound messages to restrict or support transactions. When GS02/GS03 values are given under operation binding with the Allow All Operations check box unselected, only transactions containing the GS02/GS03 pair given under the operation binding are supported to be sent or received.

If this condition is not met, transactions are restricted and they are neither sent nor received.

Inbound

Raw EDI Segments
Include in Private Process Request

Select this check box to include raw EDI message in the private process (RESPONDER.REQUEST) for this operation.

By default, this check box is not selected.
Include in Validation Error Advisory

Select this check box to include raw EDI messages in the Validation Error advisory.

By default, this check box is selected.
Extra Transaction Info Specify a value used to send any information to the private process at transaction level of RESPONDER.REQUEST message. It can also be included in RESPONDER.INTERCHANGE and Validation Alert advisory.
Security Option (MIME Encode Message Only)

Select one item from the list to support or deny only this transaction. The Security Option is at the transaction level. If the incoming document contains multiple transaction sets, the transaction that does not match the security option is not sent to the private process.

This does not affect acknowledgment creation for the incoming X12 document.

The options are:

  • None
  • Plain Text Only
  • Signed Only
  • Encrypted Only
  • Signed and Encrypted

Guideline

In Guideline tab, you can change or remove Validation Guidelines as explained in the following table:

Override Settings for Notify: Guideline
Field Description
Validation Guideline
Guideline File for validating X12 Partner data (.sef or .std) Click change to select and load the guideline file associated with this message type. Then, follow the procedure described in TIBCO BusinessConnect™ Container Edition Trading Partner Management, File Specification Dialog. The guideline file associated with this message type.
Validator Profile File (.apf) Click change to select and load the Validator profile file. Validator profile files are used to check errors and categorize them to different levels of severity. For details, see Configuring Validation Profile (.apf) Files.
Allow Dynamic Guideline Loading based on GS02 Sender/GS03 Receiver

If you select this check box, the guideline associated with this message type is determined by the GS02 and GS03 value in the message, and loaded from file system, rather than using the default guidelines specified in Guideline File for validating X12 Partner data.

You can use the GS0203_guidelines.map file in the root/bcce-edi-1.0.0/config/ directory to predefine the guideline file name for each GS02/GS03 pair. The format of each line of the file is: Key = full path of guideline file. See this file for more details.

The original guideline file name defined in Guideline File for validating X12 Partner data and GS02 Sender/GS03 Receiver Group Headers in the message are used to form the Key to search in this file. Search is conducted in the following order:

  1. Original file name_GS02 Sender_GS03 Receiver If a key that matches the original guideline name and both the GS02 and GS03 values, the file path in this line is used for loading the specific guideline file.
  2. Original file name_GS02 Sender If the key in step 1 is not found, the key that matches the original name and the GS02 value is picked up, and the file path in this line is used.
  3. Original file name_GS03 Receiver If the key in step 2 is not found, the key with the original name and the GS03 value is picked up, and the file path in this line is used.

Note:

  • Duplicate Keys are not supported in the map file.
  • If no key matches, the default guidelines specified in Guideline File for validating X12 Partner data are used.
  • If any character exists in GS02 and GS03 that is not permitted for file path, such as / \\ : ? * \ < > |, and spaces, these characters are all replaced by underscores (_) to form the search key.

Schema

In Schema tab, you can change or remove the Map file as explained in the following table:

Override Settings for Notify: Schema
Field Description
Transaction Schema (.xsd): The message schema required for the EDI conversion engine. When a connection to TIBCO BusinessConnect Container Edition is created in TIBCO Business Studio, loading the message schema into the TIBCO BusinessConnect Container Edition configuration store allows it to be retrieved automatically by TIBCO Business Studio.
EDI to XML translation Map file (.map):

Click Upload file to select and load the EDI to XML translation map file associated with this message type.

Note: EDI to XML translation map files have the extension _EX.map.
XML to EDI translation Map file (.map):

Click Upload file to select and load the XML to EDI translation map file associated with this message type.

Note: XML to EDI translation map files have the extension _XE.map.