Dynamic routing built-in functions (labelled “TDMRelated” in the Built-in Filter Functions window), allow you to add, delete, or specify destinations for a transaction that are not originally part of the transaction’s route. You can use only destinations or a distributed SFM already defined to the local SFM through destination ID records in the SFM’s configuration file.
If one of the destinations you add or specify is a NullDest,
or if the transaction ID record in the SFM configuration file specifies
a NullDest, only the NullDest is
used. Other destinations are ignored.
If the SFM does not recognize a destination as valid, the transaction fails production object qualification. These filter functions do not change the SFM configuration file in any way.
Use a dynamic routing function only as part of a post-qualification
rule. Any other rule that uses a dynamic routing function is ignored.
When a transaction qualifies for multiple production objects and one or more of those production objects uses dynamic routing, the SFM rejects the transaction.
Adds a destination to those already specified for this production object’s output. You can specify up to ten destinations per use of this function, and each destination name can be up to 32-characters long.
Use only one of the available argument fields to identify
the destination to be added to the destination list. Use a carat
(^) character to separate each destination name in the argument
field; for example “MQB1^MQB2^DST7”.
Literal – the name of the destination as listed in the SFM configuration file.
FieldObj – the name of a field object that contains the destination names.
Datalink – the name of a datalink object containing the destination names.
Uses the contents of the current blob to add a destination to those already specified for the production object’s output. The contents of the blob can specify up to ten destinations to add, and each destination name can be up to 32 characters long. Each destination must be separated with a carat (^) character.
None.
Deletes a destination for this production object’s output. You can specify up to ten destinations to delete per use of this function. Use a carat (^) character to separate each destination name in the argument field.
Use only one of the available argument fields to identify
the destination or distributed SFM to be removed. Use a carat (^)
character to separate each destination name in the argument field;
for example “MQB1^MQB2^DST7”.
Literal – the name of the destination or distributed SFM as listed in the SFM configuration file.
FieldObj – the name of a field object containing the destination names.
Datalink – the name of a datalink object containing the destination names.
Uses the contents of the current blob to delete a destination for this production object’s output. The contents of the blob can specify up to ten destinations to delete. Each destination must be separated with a carat (^) character.
None.
Overrides all previous destinations specified for this production object’s output with the destination listed in the argument field. You can specify up to ten destinations per use of this function, and each destination name can have a maximum of 32 characters. If you need to specify additional destinations, multiple calls of the setDestName() function should be used. Use a carat (^) character to separate each destination name in the argument field.
Use only one of the available argument fields to identify
the destination to be used as the destination list. Use a carat
(^) character to separate each destination name in the argument
field; for example “MQB1^MQB2^DST7”.
Literal – the name of the destination or distributed SFM as listed in the SFM configuration file.
FieldObj – the name of a field object that contains the destination names.
Datalink – the name of a datalink object containing the destination names.
Overrides all previous destinations specified for this production object’s output with the destination listed in the contents of the current blob. The contents of the blob can specify up to ten destinations, and each destination name can be up to 32 characters long. To specify additional destinations, use multiple calls of the setDestNameData() function. Each destination must be separated with a carat (^) character.
None.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
