The WHERE clause of a FlexibleSearch statement

A limitation of the types and attributes a user can see or edit in the Backoffice Administration Cockpit

A way to assign access rights to users and user groups

A fragment of the WHERE clause of a FlexibleSearch statement

SAP Commerce delivers small jar archives called Hot Fix for the extension that fixes a specific bug.

SAP Commerce provides an extension that contains bug fixes.

SAP Commerce provides SAP Notes with code corrections describing the best way to fix a specific bug.

SAP Commerce provides a patch release that contains only bug fixes and security patches.

Set a reference to a specific job implementation within the CronJob.

Assign a CronJob to a group of nodes to run on a configured node group.

Configure a trigger to run at a specified time.

Assign a CronJob to run on a node with a specified ID.

Configure the auto reconnect property in the JDBC properties to reconnect to the database automatically.

Modify the FlexibleSearch query that fetches catalogs to fix the syntax errors.

Increase the number of connections in the pool if the current number is NOT sufficient.

Fix the missing links between related items in the catalog.

SAP Commerce converts LDAP query results to ImpEx.

SAP Commerce imports user and group data from an external LDAP system.

SAP Commerce can use the DSML protocol within LDAP.

SAP Commerce writes actions to the connected LDAP system.

Use the ... tag as a representation of the relationship between entity types.

Use ComplexType and EdmSimpleType as part of the ... tag.

Define the structure of the payload that the Integration API will support for both inbound and outbound requests.

Update the EDMX schema by downloading it, changing it, and re-uploading it within the SAP Commerce Backoffice.

Use odata2webservices to get the EDMX schema for the integration object.