Producer eSpace Life Cycle

If your eSpace is being used as a producer (eSpace or Extension that owns an element and exposes it for other eSpaces usage, thus called Consumers) by other consumer eSpaces (eSpace that uses an element exposed by a Producer. In this context, the element is called an eSpace reference), Service Studio provides you with the mechanisms that allow you to test the producer functionality in the context of one of its consumers. This feature is very useful when the producer itself does not have screen flows where you can check its behavior, making it necessary to be in a consumer context with the necessary screen flows.

Entry eSpace

In the Producer eSpace life cycle you can, in fact, specify whether your eSpace is to be executed in the context of the eSpace itself or in the context of any consumer. In Service Studio this is called the Entry eSpace, which indicates the point where the end-user interactions begin. See Entry eSpace.

Like any eSpace, the producer eSpace life cycle also includes the personal cycle and the team cycle. This means that you can first develop your producer eSpace in your Personal Area, and then afterwards, whenever you feel it is ready, publish the eSpace.

Personal Cycle

The personal cycle allows each developer to design their own eSpace but, since the eSpace has no interface, you have to execute it in the context of an Entry eSpace. Therefore, whenever you run your producer eSpace, it is also necessary to spread these changes to the consumer you selected an Entry eSpace, updating its Personal Area.

The Personal cycle, fully supported by Service Studio, is divided into the following steps:

Design the eSpace in your workspace. See how to Design the eSpace.
Select the Entry eSpace (When executing the eSpace, an Entry eSpace is the consumer eSpace where the end-user interactions begins. ) in the eSpace menu. Afterwards, the Entry point drop-down, available on the Toolbar, presents all the entry points for the consumer eSpace you selected.
Run the eSpace in the Personal Area of the Entry eSpace, specified in step 2. See how to Run the eSpace.

If the changes in the public elements of your producer are such that the references, in the consumer, become modified, it is not possible to continue hosting the producer exclusively only in your Personal Area. In this situation, you have to 1-Click Publish the producer eSpace, open the consumers and handle the modified references, and 1-Click Publish these eSpaces.

Collect the feedback from this personal test and do one of the following:

Return to step 1.
Publish your eSpace making it available to all consumers, as explained below in the Team cycle.

Once you have run the eSpace in your Personal Area, you can execute it. See Execute your eSpace.

Team Cycle

Once you have run your eSpace and tested it in the context of a consumer eSpace, you simply have to publish it in your Publish Area in order to make the new version available to all consumers.

The Team cycle, fully supported by Service Studio, is divided into the following steps:

Design the eSpace in your workspace. See how to Design the eSpace
Publish the eSpace in the Publish Area of the producer eSpace. See 1-Click Publish.

In this situation, the Personal Area of the Entry eSpace is not updated. In order to execute the producer in the context of a consumer, you have to explicitly 1-click publish the consumer.

Note, however, that only after 1-click publishing the consumers, are they effectively using the new version of the producer.