
|
|
1. The renderer has methods for processing certain associations (viz., option set option links, option set member links and option set choice rule links) besides the option set itself.
2. With the Windchill ESI preference Enforce Distribution Target set to Yes, the renderer aborts the transaction if the option set is being published as a standalone object and has no distribution targets associated to it. By standalone object is meant an option set that is either published in the object centric mode, or in association with a change notice or a promotion request. This will correspond to the case where the attribute context is null.
3. With the distribution target attribute Publish the Associated Option Set when Publishing an Object to Yes, ESI services will process the assigned option set (if any), upon publishing a business object (such as a configurable part). However, in order for ESI services to process an option set assigned to a non-configurable part, the distribution target attribute Publish the Associated Option Set when Publishing a Non- configurable Object should be set to Yes, besides the previously said attribute.
4. With the distribution target attribute Publish only Incremental Changes for a Modified Option Set set to Yes, publishing a modified option set results in only the incremental changes made to the option set (since it was last successfully published) being sent with the ESI response. However, with the attribute set to No, the modified option set and all its related objects (choices, options, choice rules and the relevant associations) are sent as added objects in the ESI response.
5. Upon publishing an option set, its related choices, options, choice rules and the relevant associations are published as well. The option set renderer makes use of OptionRenderer and ChoiceRuleRenderer for this purpose.
6. A couple of other renderers viz., AssignedOptionSetLinkRenderer and ExpressionRenderer are used by Windchill ESI services for processing assigned option sets (and their associations) and expression rendering respectively.
|
|
|
1. The renderer processes all the choices that belong in an option, although only some of those choices may really be associated to the option set being published.
2. There will be an <Class_structure_relationship> element in the ESI response for each choice that is associated to the option set being published.
3. With the distribution target attribute "Publish only Incremental Changes for a Modified Option Se" to Yes, the options and choices are sent as added objects only when they are being published for the first time; they are processed as changed objects if they have changed since their last publication, and as unchanged objects otherwise. However, with the said attribute set to No, the options and choices are always sent as added objects.
4. Although the renderer has been designed to cater to a standalone option and its choices, publishing such an option is currently not supported.
|
|
|
1. The renderer processes only the following types of choice rules - Include, Enable and Exclude. Both global and local rules are processed.
2. The renderer has methods for processing certain associations (viz., rule member links and rule member action links) besides the rules themselves.
3. With the distribution target attribute Publish only Incremental Changes for a Modified Option Set set to Yes, choice rules are sent as added objects only when they are being published for the first time; they are processed as changed objects if they have changed since their last publication, and as unchanged objects otherwise. However, with the said attribute set to No, the choice rules are always sent as added objects.
4. Similarly with Publish only Incremental Changes for a Modified Option Set distribution target attribute set to Yes, the option set choice rule links, rule member links and rule member action links are sent as added, deleted, changed or unchanged associations, depending on previously published history and also the output from the object comparison framework. However, with the said attribute set to No, the said links are always sent as added associations.
|
|
|
1. In order for an assigned option set to be processed when publishing a configurable part, the distribution target attribute "Publish the Associated Option Set when Publishing an Object" must have a value Yes. However, when publishing a non-configurable part, the distribution target attribute Publish the Associated Option Set when Publishing a Non- configurable Object must have a value Yes, in addition to the above mentioned setting.
2. When publishing a business object together with its assigned option set for the first time, an association named OptionSetAssignmentHistory (that links the business object with the option set) is created in the database; however, if a previously published iteration of the business object exists at the time of publishing the object, the difference information (in terms of added/deleted option set assignment history) is computed and processed appropriately.
3. If the renderer determines that the assigned option set is not already processed, it creates an OptionSetRenderer instance and invokes the getOptionSet() API on it for processing the option set, its related objects and associations.
|
|
|
This render will always render expressions only as added i.e. expression that exists currently on object in ESI response. Distribution target attribute Publish only Incremental Changes for a Modified Option Set has no effect on the processing of this renderer.
|
