Defining Schemas

Once we have categorized the nodes and created an Attribute master list consisting of all relevant attributes applicable for the Catalog, we can start defining the schemas. Here, we will identify which Product Attributes are relevant to which Node and define them in a Schema. A schema will be useful for describing SKUs within the same product type as each SKU will have a schema with defined attributes and permitted values.

Once you open the catalog, the SKU view is displayed in the middle panel of the screen, by default. Click the Schema tab to switch to the schema view as shown below to perform all tasks related to schemas.

All the schemas are created here. You can add, edit, delete schema attributes, create schema validation constraints, add/remove attributes to PF and so on as detailed in the following sections:

• Adding Schema using Astro Intelligent Data Model Configurator

• Adding Schema Attributes to a Node

• Editing Schema Attributes in a Node

• Deleting Schema Attributes from a Node

• Copying Attribute Characteristics of a Schema

• Adding /Removing Attributes To/From a PF

• Downloading all Assets Linked to Schema Attributes in a Node

• Editing Assets Linked to Schema Attributes in a Node

• Changing the Table Setting for Schemas

The following table lists the privileges required to perform various functions related to schemas.

Table 11: Schema level privileges

*Prerequisites – This column lists the privileges that needs to be enabled first before granting the actual privilege

Let us understand how to perform each of these operations in the following sub-sections.

Adding Schema using Astro Intelligent Data Model Configurator

The PCC catalog administrator often struggles to define schema attributes and constraints effectively, typically lacking a data-driven decision-making process.

Astro Intelligent Data Model Configurator provides intelligent help and recommendation from the system on how to set up the schema for each node in the catalog. This option will only be available when Astro is enabled for the catalog.

The Astro Intelligent Data Model Configurator performs data profiling of existing SKU data in the catalog/taxonomy to come up with recommendations based on pre-defined thresholds. You will be navigated to a screen with the recommendations along with the underlying data analysis that led to the recommendations.

To add schema attributes using Astro Intelligent Data Model Configurator:

1. Follow steps 1 to 3 as mentioned in section Creating a Taxonomy Structure using Astro. The Astro icon is now enabled in the Schema view as shown below.

2. Select the node in the taxonomy panel for which you need to add schema attributes. For example, we have a node Casual Pants for which we need to add schema attributes as shown below.

If there are Global Attributes in the attribute master, it will appear by default for every schema of the node.

3. Click on Astro Intelligent Data Model Configurator.

You’ll land on Astro Intelligent Data Model Configurator for Node > “node name”.

4. There are two tabs displayed i.e. Recommended Schema Attributes and the other for Non-Recommended Attributes with counts. The default toggle will be Recommended Schema Attributes.

A list of schema attributes suitable for the node selected is displayed. In this case, since the node selected was Casual Pants, attributes such as Color, Prize, and so on are displayed.

5. You can see the Thresholds that are set for the selected taxonomy with each parameter count as shown in the below image.

6. You can click   Modify thresholds, to edit or modify the thresholds for the schema.

The following pop-up with certain parameters gets displayed.

• Minimum Presence for Schema Inclusion: Here you can enter the minimum percentage required attributes for all SKUs within a taxonomy to be considered a schema attribute.

• Minimum Presence for Is Required: Here you can enter the minimum percentage of an attribute across all SKUs in a taxonomy required for a 'is-Required' schema constraint recommendation.

• Maximum Distinct Value Count for LoV Consideration: Here you can set maximum distinct values for a taxonomy-attribute combination needed for an Enforce-LOVs schema constraint recommendation.

• Maximum Distinct Value Count for UoM Consideration: Here you need to enter the maximum possible distinct units of measure found for a taxonomy-attribute combination which allows the schema design helper to suggest Enforce-UoM schema constraint recommendation.

Note: None of the threshold values can be left empty as it will throw error and you’ll not be able to proceed as the Re-run recommendations button will be greyed out.

7. Once you have added the thresholds, click Re-run recommendations and to retain the existing values click Cancel.

   You’ll get a refined list of Recommended & Non-Recommended schema attributes based on the threshold value.

   Following are the components on the Recommended Schema attributes:

• Attribute-> displays the attribute name along with the datatype such as ST (string) or IN (Integer) as shown in the below screenshot.

• Include Schema? -> This option is used to add bulk attributes in schema by checking/unchecking the checkbox near Include in Schema field label as shown in the screenshot below, this flag is a pre-requisite and needs to be checked to add the constraints. This flag needs to be checked if you need to add constraints.

Here if they include schema is checked for parent and child node, its constraints will automatically reflect the parent node selection. You cannot have a different selection if the parent and child are selected or can make an individual selection for a child node if the parent is not selected.

Note: If immediate parent is checked, you will not be able to uncheck the child node nor edit, only if you uncheck the parent, or if the parent is not recommended but recommended in child then the node level control is editable.

• Under Recommended for Constraints you can view various constraints such as Is required, Enforce LoVs, Enforce UoMs, Enforce Datatype, Enforce Min-Max value, Enforce Min-Max character Length. Each constraint will automatically be enabled depending on the threshold values that were set. For more information on why it is recommended can be seen in each cell when you hover over on the   icon as demonstrated in the below screenshot.

If the constraint is not recommended, then it will say it is not recommended as demonstrated in the below screenshot.

• For constraints such as Enforce LoVs or UoMs, they are aggregated from the SKU attribute value for that node. You can select all or handpick and then the count will be seen.

• For Enforce Min/Max value or character length, the predefined value is based on the SKU data which will be initially displayed. You can click on the  (eye) icon to edit the values.

You can see the node structure and hierarchy upon clicking on the  (eye) icon near the taxonomy node name as shown below.

• The Non-Recommended Attributes tab is a read-only list of attribute names and the reasons they weren't recommended as shown in the below screenshot. No actions can be taken on this page.

8. Once all the constraints are set & reviewed then click Save.

   You’ll see a pop up as Updating Schema Attributes for the node “name” and land on the Schema tab as shown in the screenshot below.

Adding Schema Attributes to a Node

The first step in defining schemas is to add schema attributes to a node selected, that is, you can add all the attributes from the attribute master list / attribute master group relevant for the selected node / add a new attribute here. You can add one or multiple attributes as required.

For example, we have a node Sunglasses and Frames under Accessories. Let us define a schema for Sunglasses and Frames.

To add schema attributes to a node:

1. In the Schema view, click the Add Attributes(s)icon as shown below:

OR

Right-click the schema grid and then click Add Attribute(s) as shown below.

The following screen appears:

Let us understand the type of information to be added in each of the fields. You can add attributes in 2 ways:

• Existing Attributes - As soon as you start typing the Attribute Name of the attribute to be added, the list will auto populate based on the attributes defined in the attribute master list.

• New Attribute – You can add a new attribute which is not present in the attribute master as well. In this case, the attribute will be added to the attribute master too, by default.

Case 1: Add existing attributes from the attribute master list. For example, in the case of Sunglasses and Frames, let us add an attribute Frame Material which is already present in the Attribute Master list.

1. Type the Attribute Name as Frame Material. The following screen appears.

The schema information is displayed automatically based on the attribute information that is predefined while creating attributes. Now, you can make changes if any, or continue with the same.

2. Enter the relevant schema information as shown below:

   1. Attribute Name: This is auto populated from the attribute master list. Note: In case of a new attribute being added, you can enter the name as needed.

   2. Customer Attribute Id: This field is disabled for attributes present in the attribute master list. Note: In case of a new attribute being added, you can enter the Id as needed.

   3. Attribute Description: Enter the description for the attribute. For example, an attribute Frame Material can have a description as ‘material of the frame used for sunglasses. This field can be used to provide information on the type of attribute. However, this field is not mandatory and can be kept blank as well.

   4. Navigation OrderNavigation Ordere order of the attributes here, that is, the order in which the attributes will appear on the e-commerce site.

      Note: You can only enter integer values such as 1,2 and so on.

   5. Auto Cascade: Turn on the toggle, if an attribute needs to be inherited by all the nodes in the hierarchy automatically. Refer to the Schema Inheritance section for more details.

   6. Schema Constraints: Refer Schema Constraints section for more information.

3. Meta Tag (Optional): Select the appropriate meta tag for the attribute from the drop-down list, if needed. Note: If an attribute selected is already associated to a meta tag while attribute creation, it will automatically reflect here. You can change the meta tag as needed or add more meta tags.

4. Meta Attributes (Optional): Select the appropriate meta attribute for the attribute from the drop-down list, if needed.

   Note: If an attribute selected is already associated to a meta attribute while attribute creation, it will automatically reflect here. You can change the meta attribute as needed or add more meta attributes.

5. Click the +Add Attributes icon to add multiple schema attributes for the node as shown in the screenshot below:

6. Similarly, for the added schema attribute, you can click the Remove Schema Attribute icon in case you need to remove any attribute.

7. If you want to apply the same characteristics to the rest of the schema attributes, click on the Apply this schema characteristics to all icon and a list options as shown below gets displayed:

8. Select the appropriate option and you’ll see a pop-up as All the characteristics are applied successfully.

9. Click on on icon to quickly locate or search the attribute.

10. Review the attribute details and constraint settings.

11. Click Save to add the attribute to the selected node.

12. The attribute will now appear in the node’s schema attribute list.

    

Schema Constraints

This feature enables you to create validation rules that will ensure that while creating SKUs, any incorrect value is not accepted based on the constraints set in the schemas.

The following table lists the schema constraints that can be set while defining schema attributes.

• Enable Constraints? (column header): A toggle for the respective schema constraints that turns the constraint enforcement on or off for this attribute. If disabled, no constraints are applied.

Best practice: Keep this enabled if you want any validation. Disabling it turns off all checks.

• Is Conditional? (column header): A toggle indicating whether the constraint applies conditionally (e.g. only if another attribute has a certain value). Purpose: Advanced; typically leave off unless using conditional logic (exact behaviour may depend on system UI.

• Constraint Configuration (column header): Contains the actual settings or values for each constraint when enabled (for example, a datatype dropdown, min/max fields, LOV picker, etc.). Details follow per constraint:

The above-mentioned schema constraints will ensure that while using the schemas during SKU creation, any invalid entry will result in a validation error based on the rules set for each schema.

In case of multiple LoVs for a schema attribute added, click the View All option to view the complete list of values present for an attribute as shown below:

Case 2: Add new attributes which are not present in the attribute master list. For example, let us add an attribute Paint.

1. Type the Attribute Name as Paint and a message is displayed stating that this attribute will also be added to the Attribute Master as shown below:

   

2. Add all the other relevant information as explained in steps 2 to 10 in Case 1 and add the schema.

   Note: In case of a new attribute being added, you have the option of changing the data type for an attribute. Also, the Customer Attribute Id field is enabled and you can add the Id for the attribute here. In this case, since it is a new attribute being added, it will be added in the attribute master list as well.

   However, if the review mode is turned on for user action Review the addition of new schema while adding/editing a hierarchy, a schema attribute cannot be added directly as it will be assigned to a reviewer. In this case, while adding a new schema attribute, a message is displayed as follows.

For example, a schema attribute Face Shape is added. A green icon is now displayed next to the schema attribute which indicates that approval to add the schema is pending as shown below.

This indicates that the schema to be added is sent to the reviewer for approval.

Depending on the action taken by the reviewer, the request will be approved / rejected /aborted as explained in section Reviewing the User Actions Assigned.

Schema Inheritance

Certain node-attribute relations are such that several nodes under a single parent will have many common attributes as a schema. In this case, they can be cascaded from a higher-level node to its children, that is, you can create the schemas at that parent node which will be inherited by all nodes in that hierarchy automatically.  This concept is called schema inheritance, which allows the user to define the schema once at a higher-level node, and then indicate the system to inherit the schema across all the children nodes, thereby increasing work efficiency.

The inheritance is “live”, that is, if the schema definition in the parent is modified, that change is also inherited in real time in the child nodes.

For example, Accessories is a parent node with Sunglasses and Watches as its branch nodes. An attribute Brand is common to both Watches and Sunglasses and should exist in all the child nodes as well. Thus, while defining a schema for Accessories, we can set the Auto Cascade option for the attribute Brand as shown below.

After a schema attribute is added, the attribute Brand is indicated by a downward arrow icon in purple color as shown below, indicating that this schema attribute is now inherited by all nodes under the parent node.

Also, the child nodes will automatically inherit the schema attribute Brand and it is indicated by an upward arrow icon in green coloras shown below which means these are inherited attributes.

Following are some important pointers with respect to inherited schemas:

• All the child nodes that have inherited schemas will function like any other schemas. If the Auto Cascade option is cleared from the parent schema, the inherited schemas will not be deleted. In this case, the schema attribute Brand will continue to exist in Sunglasses and Watches node.

• You can edit schemas in the child node and change any attribute value. However, if the parent node has Auto Cascade enabled and any changes are made in the schema, the changes will automatically overwrite changes made in the inherited schemas.

• An inherited schema definition can be configured to be inherited from only one parent schema, where this parent may be any node in the upper hierarchy of the taxonomy structure. So, it is not allowed for a mid-level parent to also be configured to inherit down.

For example, the nodes Sunglasses and Watches have child nodes Rectangular and Analog respectively. Accessories is the parent node within which all these nodes exist.  If node Accessories has a schema attribute (Brand) which is configured to be auto inherited, the nodes Sunglasses and Watches as well as all nodes within this (Rectangular and Analog) will inherit the schema attribute Brand. Now, you cannot configure the same schemas in the nodes Sunglasses and Watches to be inherited as it is already an inherited schema. The Auto Cascade option will be disabled for nodes Sunglasses and Watches for the attribute Brand. Only, if you clear the Auto Cascade option from the schema attribute Brand in Accessories node, you can configure the schemas in the nodes Sunglasses and Watches to be inherited further.

However, you can create a new schema attribute for nodes Sunglasses, say Warranty. You can configure the schema attribute Warranty to be auto inherited and the node within Sunglasses, that is, Rectangular will inherit this schema attribute Warranty.

Editing Schema Attributes in a Node

You can edit the schema attributes added in a node.

To edit schema attributes in a node:

1. Select the schema attribute and then select the Edit Schema(s)  icon or right-click the attribute and then click Edit Schema(s). The following screen appears.

2. Make the necessary changes as needed. You cannot edit the Attribute Name / Customer Attribute Id / select a different Data Type. You can edit the Description, enable other schema constraints as well as change the settings for Auto Cascade.

3. For example, a schema attribute Frame Material is edited. A purple

Thus, the schema to be edited is sent to the reviewer for approval. The editing can be any changes in the schema attribute such as LoV / UoM values modified, schema constraints added/ removed and so on.

Depending on the action taken by the reviewer, the request will be approved / rejected /aborted as explained in section Reviewing the User Actions Assigned.

Deleting Schema Attributes from a Node

You can delete the schema attributes created. However, deleting a schema attribute will only delink attributes and its details from the schema. The attribute will exist in the attribute master list.

Also, if the schema attribute deleted is a derived attribute which is present in the SKU as well, the UoM value for that derived attribute used in SKU will now change to what is defined in the attribute master for that derived attribute. If no UOM is defined in the attribute master for that derived attribute, the UoM is also removed in the SKU value present in the node for which the schema was deleted.

To delete a schema attribute:

1. Select the schema attribute and then select the Delete Schema(s) icon or right-click the attribute and then click Delete Schema(s).

2. Click Yes if you want to delink attributes and its details from the schema and the schema attribute is deleted successfully. Once deleted, these attributes will not be populated in export.

However, if the review mode is turned on for user action Review the deletion of a schema while adding/editing a hierarchy, you cannot delete the schema attributes directly as it will be assigned to a reviewer. In this case, while deleting the schema, a message is displayed as follows.

Figure 102: Action under review message

For example, a schema attribute Brand is deleted. In this case, the schema attribute is not deleted and a red icon is now displayed next to the schema which indicates that approval to delete the schema is pending as shown below.

Depending on the action taken by the reviewer, the request will be approved / rejected / aborted as explained in section 19.4 Reviewing the User Actions Assigned.

Copying Attribute Characteristics of a Schema

You can copy attributes/ entire schema of the node to a different node or copy attribute characteristics to an attribute in the same/different node with all UoMs, LoVs and constraints or without these elements based on the requirements.

Following are the various options available:

• Copying Entire Schema of Node

• Copying Attributes

• Copying Attribute Characteristics

Copying Entire Schema of Node

Here, you can copy the entire schema of the selected node, that is, all the schemas defined for a node will be copied to the destination node. However, you can select whether you want to copy the UoMs, LoVs and constraints along with it.

To copy the entire schema of a node:

1. Select the node from where the schema is to be copied.

2. Go to the Schema view and then select the Copy Attribute Characteristics  icon and then click Copy Entire Schema of Node. Following are the options available:

• With All (UoM(s), LoV(s), Constraints) – Select this to copy all UoMs, LoVs and Constraints set for the entire schema

• With None of (UoM(s), LoV(s), Constraints) – Select this if you do not want the UoMs, LoVs and Constraints to be copied along with the schema.

• With Only Constraints – Select this to copy only the constraints defined for the schema

• With Attribute UoM(s) & LoV(s) – Select this to copy only the attribute specific UoMs and LoVs

For example, let us copy the entire schema of Sunglasses to the Rectangular node.

Figure 103: Selecting the node to copy entire schema

Let us assume that we select the node Sunglasses and then select the Copy Attribute Characteristics icon > Copy Entire Schema of Node > With Only Constraints.

3. Select the node where you want to copy the entire schema with only constraints. For example, we select the node Rectangular. The following screen appears.

Figure 104: Pasting entire schema to a node

The Paste Attribute Characteristics icon is enabled.

4. Click the Paste Attribute Characteristics icon and then click Paste Entire Schema of Node > With Only Constraints as shown below.

The entire schema is copied with only the constraints as selected. Similarly, you can choose the elements needed and select the respective option.

Copying Attributes

Here, you can copy the attributes of the selected node, that is, you can select the attributes defined in a schema for a node to be copied to the destination node. However, you can select whether you want to copy the UoMs, LoVs and constraints along with it.

To copy the attributes of a node:

1. Select the node from where the schema attribute is to be copied.

2. Select the schema attribute to be copied. You can select multiple attributes too.

3. Go to the Schema view and then select the Copy Attributes Characteristics  icon and then click Copy Attributes. Following are the options available:

• With All (UoM(s), LoV(s), Constraints) – Select this to copy all UoMs, LoVs and Constraints set for the attribute

• With None of (UoM(s), LoV(s), Constraints) – Select this if you do not want the UoMs, LoVs and Constraints to be copied along with the attributes.

• With Only Constraints – Select this to copy only the constraints defined for the attribute

• With Attribute UoM(s) & LoV(s) – Select this to copy only the attribute specific UoMs and LoVs

For example, let us copy the attributes from the Rectangular node to the Aviator node.

Figure 105: Copying attributes of a node

4. Let us assume that we select the node Rectangular and then select the attributes Paint and Description. Click the Copy Attribute Characteristics icon > Copy Attributes > With Attribute UoM(s) & LoV(s). The schema is copied.

5. Select the node where you want to copy the schema attributes selected with UoMs and LoVs. For example, we select the node Aviator. The following screen appears.

Figure 106: Pasting attributes to a node

The Paste Attribute Characteristics icon is enabled.

6. Click the Paste Attribute Characteristics icon and then click Paste Attributes > With Attribute UoM(s) & LoV(s).

   The selected attribute is copied with only the attribute UoMs and LoVs. Similarly, you can choose the elements needed and select the respective option.

Copying Attribute Characteristics

Here, you can copy the attribute characteristics of the selected attribute to a different attribute within the same node. For example, a node Analog has three attributes (Dial Width, Strap Width and Color). We need to copy the attribute characteristics of Strap Width to Dial Width. Let us understand how we can do this. Also, you can select whether you want to copy the UoMs, LoVs and constraints along with it.

To copy attribute characteristics of an attribute:

1. Select the node from which the attribute characteristics are to be copied.

2. Select the attribute whose attribute characteristics are to be copied.

3. Go to the Schema view and then select the Copy Attribute Characteristics  icon and then click Copy Attribute Characteristics. Following are the options available:

• With All (UoM(s), LoV(s), Constraints) – Select this to copy all UoMs, LoVs and Constraints set for the attribute

• With Only Constraints – Select this to copy only the constraints defined for the attribute

• With Attribute UoM(s) & LoV(s) – Select this to copy only the attribute specific UoMs and LoVs

For example, let us copy the attribute characteristics of Strap Width to Dial Width from Analog node.

Figure 107: Copying attribute characteristics of a node

4. Let us assume that we select the node Analog and then select the attribute Strap Material. Click Copy Attribute Characteristicsicon > Copy Attribute Characteristics > With Only Constraints.

5. Select the attribute within the same node where you want to copy the characteristics, that is, with only constraints. For example, we select the attribute Dial Width. The following screen appears.

Figure 108: Pasting attribute characteristics to a node

The Paste Attribute Characteristics icon is enabled.

6. Click the Paste Attribute Characteristics icon and then click Paste Attribute Characteristics > With Only Constraints.

7. The selected attribute characteristic is copied with only the constraints as selected. Similarly, you can choose the elements needed and select the respective option.

Adding /Removing Attributes To/From a PF

A Product Family (PF) is very similar to an Attribute Master Group. An Attribute Master Group consists of a group of attributes having similar characteristics whereas a PF is a logical categorization of a group of SKUs which have minor differences with each other. Refer section Defining Product Families (PF) to know more about PFs.

In this section, we will understand how to add and remove attributes to and from a PF.

• Adding Attributes to a PF

• Removing Attributes from a PF

Adding Attributes to a PF

You can add attributes to an existing PF. Details about how to add a PF, manage it and so on is detailed in section Defining Product Families (PF).

Let us understand how to add attributes to a PF. For example, consider a node Rectangular. Let us assume that a PF is already created for all the SKUs in this node. Let us add attributes to this PF.

To add attributes to a PF:

1. Select the node from where the schema attribute is to be added to the PF.

2. Go to the Schema view and select the schema attribute to be added. For example, let us select the attribute Paint from the Rectangular node.

3. Select the Add/Remove Attribute(s) to Product Family icon and then click Add Attribute(s) To PF or right-click the attribute and then click Add Attribute(s) To PF. The following screen appears.

Figure 109: Add schema attributes to PF

The list of PF for the selected node is displayed. If a PF is not created for the selected node, then the list will have no values. Hence, it is important to create a PF first and then add attributes to it.

4. Select the PF and then click Next. The following screen appears.

Figure 110: Add values

All the attribute characteristics of the selected attribute are displayed. In this case, the values for attribute Paint are displayed.

5. Click Add More to add multiple attributes to PF.

6. Click Next. The following screen appears.

Figure 111: Confirmation screen to add attributes

A detailed information about the attribute being added to the PF along with the relevant details is displayed.

7. Click Add Attribute and the attribute is added successfully to the PF.

Removing Attributes from a PF

You can remove attributes that have been added to a PF.

For example, consider the same node Rayban. We just added an attribute to the PF in Adding Attributes to a PF. Let us remove that attribute from the PF.

To remove attributes from a PF:

1. Select the node from where the schema attribute is to be deleted from the PF.

2. Go to the Schema view and select the schema attribute to be removed. For example, let us select the attribute Paint from the Rectangular node.

3. Select the Add/Remove Attribute(s) to Product Family icon and then click Remove Attribute(s) From PF or right-click the attribute and then click Remove Attribute(s) From PF. The following screen appears.

Figure 112: Remove schema attributes from PF

The attribute name and hierarchy of the PF to which it is associated is displayed.

4. Select the PF hierarchy from where it is to be removed and then click Remove Attribute. The attribute is removed successfully from the PF.

Downloading Assets Linked to All Attributes Added in Schema

You can download assets linked to all the attributes added in schema from the attribute master list for the selected node.

To download assets linked to all attributes added in schema:

1. Select the node from the taxonomy tree and the schema attributes for the selected node is displayed as follows.

2. Click the Assetsicon and then click Download Assets as shown below to download the  assets.

The following screen appears.

The count of all assets present in all the schema attributes for the selected node is displayed. Refer section Downloading Assets for detailed steps on how to download the assets.

Editing Assets Linked to All Attributes Added in Schema

You can edit assets linked to all the attributes added in a schema from the attribute master for the selected node.  A detailed description on how to create templates required to edit the images, the various operations that can be performed on the templates and how to view the processed images is explained in section 0

Batch Editing of Multiple Images. Let us understand how to edit assets linked to schema attributes from the schema view itself.

To edit assets linked to schema attributes:

1. Select the node having schema attributes with assets to be edited. For example, a node Watches is selected which contains 2 schema attributes.

2. Click the Assets icon and then select Edit Linked Photo Assets > Linked to all Schema Attribute(s) of Selected Node as shown below.

OR

Right-click any schema attribute and then select Assets > Edit Linked Photo Assets > Linked to all Schema Attribute(s) of Selected Node as shown below.

The following dialog box appears.

There are 4 steps to be performed to edit the images. Refer section Editing Images from the DA Library for complete details on how to perform these 4 steps to successfully edit the images.

Changing the Table Setting for Schemas

You can change the setting of the columns containing the schema information.

1. In the Schema view, click the Table Settingsicon . The following options are displayed.

The following table lists the various options available to change the table settings for schema information.

Table 14: Table settings for schemas