Script properties
In Sitecore Content Hub, all types of scripts have access to two main objects: MClient
and Context
. Both MClient
and Context
objects provide users with a collection of useful properties. See the API Reference for additional information.
MClient properties
MClient
properties are available for all types of scripts. They allow users to manipulate data in Content Hub (for example, data sources, entities, entity definitions, policies, scripts, users) and other functionalities like querying and logging through different clients.
The following table summarizes the available MClient
properties:
Property |
Type |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Context properties
Context properties are the different context variables that are accessible by scripts. Each script type has specific context properties. The following section defines the context properties for each script type.
User sign-in scripts
The following table contains the context properties available for User sign-in scripts.
Property |
Type |
Description |
---|---|---|
|
|
This property contains the source of registration of the user, which can be internal (Content Hub) or external (an external provider). Possible values:
|
|
|
This property contains the entity object representing the signed-in user. |
|
|
This property contains the information about the user that the external provider supplies.
|
ExternalUserInfo
is only used when the AuthenticationSource
is External
.
User pre-registration scripts
The following table contains the context properties available for User registration scripts.
Property |
Type |
Description |
---|---|---|
|
|
This property contains the source of registration of the user, which can be internal (Content Hub) or external (an external provider). Possible values:
|
|
|
This property contains the username of the created user. |
|
|
This property contains the email of the created user. |
|
|
This property contains the culture information of the created user. |
User post-registration scripts
The following table contains the context properties available for User registration scripts.
Property |
Type |
Description |
---|---|---|
|
|
This property contains the source of registration of the user, which can be internal (Content Hub) or external (an external provider). Possible values:
|
|
|
This property contains the entity object representing the signed-in user. |
|
|
This property contains the information about the user that the external provider supplies.
|
ExternalInfo
is only used when the AuthenticationSource
is External
.
Metadata processing script
The following table contains the context properties available for Metadata processing scripts.
Property |
Type |
Description |
---|---|---|
|
|
This property contains the File entity that is being processed.
|
|
|
This property contains the entity object representing the asset associated with the File entity being processed. |
|
|
This property contains the available metadata. The metadata properties depend on the processed file. |
Action scripts
For Action scripts, the context properties depend on the execution source of the script. The execution source is the method by which the script is called. The context properties differ according to the following use cases:
-
Web Api - When the script is called by a Web Api (REST). In this case,
ExecutionSource
is equal toWebApi
. -
External Action - When the script is called by an external action from a page component. In this case,
ExecutionSource
is equal toExternalAction
orMassEdit
. It is set toMassEdit
when theAction script
is called from the mass-edit menu. -
Triggers - The context properties for triggers depend on their execution type: In Process or In Background (Out of process).
-
In Background - When the script is called by a trigger in background. In this case,
ExecutionSource
is equal toTrigger
andExecutionType
is equal toOutOfProcess
. -
In Process - When the script is called by a trigger in process. In this case,
ExecutionSource
is equal toTrigger
andExecutionType
is equal toInProcess
.
-
For each use case, click the tab to see a table that contains the relevant context properties.