Segments

In the Emptoris Supplier Lifecycle Management application, segments are the representation of a business rule applied to a client request. Segments are module specific and cannot be combined with different modules.

Segments consists of a business rule and presentment rule. The following representations are available for segments in the Emptoris Supplier Lifecycle Management application:
  • xml
  • json
  • xhtml
You must consider the following points with regards to segments:
  • A segment consists of a business rule, layout rule, and representation in the form of XML, JSON or XHTML.
  • A segment is the representation of a business rule applied to a client request. It might contain a set of parameters like suppliers, categories, and more or is send without additional parameters.
  • A request to a segment invokes the business rule configured for the particular segment.
  • A segment is module specific and cannot be combined with other modules.
  • A segment depends on a specific master data business object. For example, suppliers, categories, organizations, and more.
  • The information received is filtered based on the user's permissions.

You can go to the Emptoris Supplier Lifecycle Management application by clicking the direct link in a segment. The direct links must be provided for non-average results. For example, latest evaluation result, latest risk score, and more.

If there are average scores configured in the segment, then the links are not generated.

Conjoint Segment Resources

You can combine multiple segments to create a conjoint segment in the Emptoris Supplier Lifecycle Management application. It is a container for existing segments to provide multiple results within one HTTP GET request.

You must consider the following points with regards to conjoint segments:
  • Segments from different modules can be combined, but the base pillar in the selected segments must be the same.
  • You can configure more than two conjoint segments at a time. If your system has too much data then it is not recommended to configure multiple conjoint segments as it might lead to performance issues.
  • Conjoint segments cannot be configured for Area resources.

The following is an example to configure the conjoint segment:

<bean id="sup-segment-container" class="com.xcitec.suite.modules.restws.segments.SegmentContainer"> 
     <property name="presentment" ref="sourcingEvaSegmentPresentment"/>
     <property name="description" value="interfaces.segment.container.evaluation.average.description"/> 
     <property name="icon" value="TEST ICON"/> 
     <property name="headerTitle" value="interfaces.segment.container.evaluation.average.title"/>   
     <property name="segments">    
       <util:list>             
       <ref bean="supseg-eva-restricted-latest"/>     
       <ref bean="supseg-eva-restricted-average"/>    
       </util:list>     
     </property> 
 </bean>
 …