Siebel tools latest version

You can create, refine, or activate a query from the Query menu or from the List toolbar. You can also use shortcut keys instead of using the Query menu. The following table describes the operators that you can use to create a simple query. A simple query is a type of query that locates records according to one condition.

The Changed property is an example of a property that contains a Boolean value. For more information about query operators and Siebel data types, see Siebel Developer's Reference. Table Simple Query Operators. A wildcard. Queries for a string that includes a special character. If your query text includes a special character, then you must use quotes to enclose the query. A compound query is a type of query that locates records according to more than one condition.

You can use parentheses to control the order that Siebel Tools uses to do a compound query. Siebel Tools runs the query according to the expression that you enter. It starts with the inside parentheses and then proceeds to the next, similar to the order in which you read English. The following table describes operators that you can use for a compound query.

You can combine simple conditions and compound conditions in a single query. For more information, see Siebel Developer's Reference.

Table Compound Query Operators. Siebel Tools Online Help appears with documentation about the selected object type, including information about its properties.

The content in this online help also appears in Siebel Object Types Reference. This topic describes how to use windows, wizards, and toolbars. Using the Properties Window. Using Web Templates. Using the Multi Value Property Window. Using the Bookmarks Window. Displaying, Docking, and Stacking Windows. Using a New Object Wizard. Using the Toolbars. The Properties window is a window that displays the properties and the property value for the object that you choose in the Object List Editor.

It displays the name of this object and the name of the property in the one column and the property value in the next column. Siebel Tools displays properties in the Properties window in alphabetic order. You can click the Categorized tab to view these properties grouped according to category. The Properties window does not display the Project property or the Changed property. In this example, you use the Properties window to modify the Comments property of the Siebel Call Center application.

To verify your modifications, examine the Comments property in the Applications list. It includes the values you entered. To filter the templates, you can use the filter preceding the list of objects or run a query using the gear icon in the Object List Editor applet. To modify, you must first open a workspace. You can customize the editor with options such as auto-close tags, hints, display of line numbers or Object Design hierarchy, and indentation.

The settings you select are automatically available whenever you access the editor. The Multi Value Property Window allows you to view and set values for multi-value properties when you use one of the following designers:.

The Bookmarks window is a window that allows you to navigate directly to an object that you use frequently. For more information, see History Toolbar. In Siebel Tools, click the View menu, click Windows, and then click the window that you want to display. You can also click the Go menu, and then click Bookmarks List to display the Bookmarks window.

To prevent Siebel Tools from docking a window when you move it, you can hold down the CTRL key while you move the window. You can display a docked window, including the Object Explorer, as a tab. You can open, close, or dock a tabbed window. Siebel Tools collapses the window and displays a tab for it at the margin of Siebel Tools. Place your curser over the tab that represents the window, and then click the push pin in the window title bar.

Siebel Tools creates a single window that includes both windows, and it adds a tab that represents each window. You can click the tabs to navigate between these stacked windows.

You can reset windows to the display that Siebel Tools uses immediately after you first install it. It pins the Object Editor and the Object List Editor to their placeholders and resizes them to their original size. A new object wizard is a feature that you can use that guides you through the steps of creating a new object. It prompts you to configure the properties and objects that Siebel Tools requires according to the object type that you are creating.

You can use a new object wizard to create the following objects:. General object. For example, a business component, table, view, or applet method menu item. Applet object. For example, a list applet, form applet, MVG Applet, or chart applet. Task object. For example, a task, task applet, task view, or transient business component.

For more information about how to use a wizard for a particular object type, see Configuring Siebel Business Applications. Siebel Tools displays a list of wizards that are specific to the object type that you choose.

The following image illustrates the toolbars that you can use in Siebel Tools. A toolbar is active only if the object type or window that uses it is active. You can relocate toolbars using the mouse.

You can display and hide toolbars. Edit Toolbar. Allows you to use edit tools, the New Object wizard, and undo and redo options. You can right-click a field in the Object List Editor to display a menu of edit tools. List Toolbar. Allows you to insert a new record, move forward and backward through records, query records, and sort records.

It manages records that the Object List Editor shows. History Toolbar. Allows you to retrace your steps, and to create and navigate to bookmarks.

Debug Toolbar. For more information, see Using Siebel Script Editors. Format Toolbar. Allows you to apply a format to an applet control.

This control uses a Web template that uses a grid layout. Allows you to publish, revise, or expire a workflow process or task UI. You can activate a workflow process if you are the owner of the root workspace and the workflow is delivered into it.

Configuration Context Toolbar. Allows you to define settings for Web browser layout and scripting. In Siebel Tools, click the View menu, click Toolbars, and then click the menu item that represents the toolbar that you want to display. If Siebel Tools displays a check mark next to the menu item that represents the toolbar, then the toolbar is visible. This topic describes how to use some of the editors that you can use in Siebel Tools. Using an Editor That Includes a Canvas.

Using a Script Editor. A canvas is a background that appears in different designers. It includes a work area that allows you to move or rearrange objects. For example, the Task Designer allows you to move a Siebel Operation step from the Palette window to the canvas. The canvas also indicates whether or not you can edit an object. Siebel Tools displays the canvas as a solid grid, which indicates that you can edit the task. It displays task objects over this grid. Siebel Tools displays the canvas as a solid background with no grid, which indicates that you cannot edit the task.

Some editors, such as the Workflow Process Designer, use a colored canvas to indicate that you cannot edit the object. To choose records that are not consecutive, hold down the CTRL key while you click each record. To choose multiple records that are consecutive, click a record, hold down the SHIFT key, and then click another record.

The following table describes the editors that include a canvas. You can use these editors with the Palettes Window. Table Editors That Include a Canvas.

Allows you to diagram the business entities that your configuration uses and represent relationships between these entities. For more information, see Configuring Siebel Business Applications. Allows you to create a user interface that assists the user in completing a job task. Allows you to add steps and connectors to a task UI. Allows you to define, manage, and enforce the business processes that your company uses. Allows you to add steps and connectors to a workflow process.

If you cannot use declarative configuration to meet your requirements, then you can use the Server Script Editor and the Browser Script Editor in Siebel Tools to create a script. You use these editors to add a script to a Siebel object. You can use the following types of script:. For information about declarative configuration, see Overview of Using Siebel Tools. For information about scripting, see Using Siebel Script Editors.

Overview of Integrated Development Environment. Using a Web Page Editor. Using a View Web Template Editor. Using an Applet Web Template Editor. IDE helps you configure new applets and views or modify existing ones. You can also preview your changes from within IDE for the desired application.

Displays the view or applet you selected for update. It also has the Close button to exit IDE. Helps you view the layout in three different form factors: Desktop, Tablet, and Mobile.

This helps fine tune the layout as per your requirement and visualize the result. For example, placeholders that display in a row in Desktop will stack under each other in a column in Mobile due to restricted space. It is next to the Form Factor buttons and toggles to display more or less number of fields and columns in applets. Appearance of the border indicates that the control will display only during the Show More mode of the applet.

Lists Siebel applications so that you can select the application that will reflect your changes. You can also select a particular application in which you want to use the applet. If you select a specific application, your changes will be available for this applet only in the selected application. Before you obtain the preview, you must set the user property of the selected application. The preview displays the objects in context but without data. When you want to view the changes made in either editor with data, you need to log in to the actual application and submit the changes for delivery.

Lists preconfigured applets you can map to the selected view. To unmap, you can click the Trash icon at the far end of the applet. Displays all the web templates of a selected applet so that you can select to work on another web template from within the IDE itself.

For each web template, this pane lists Web Controls that you can use to create a control or a column. Contains placeholders to receive an object. Click the Trash icon to unmap an object and reuse a placeholder. You can resize the canvas from both the Library and Property pane sides. If you click on an empty placeholder then this section will be blank.

If you click outside a placeholder, on the canvas, then it will display the selected property of the view or applet. Click the Preview eye-shaped icon to preview the design in the same page as the object.

You sometimes have to modify an existing view to add a new applet or remove an existing one. In the Object List Editor, go to View and search for a view where you want to add a new applet.

The IDE for the view displays. Select the applet and, with the mouse button depressed, move the selected applet onto an unused placeholder then release the mouse button. The Properties pane displays the property for the new applet. For example, move it to placeholder If the placeholder is not visible, then click the plus sign on the canvas until you reach it or move to any unused placeholder.

Click the arrow button next to the Application drop-down list to preview the changes from within Web Tools. You can use Applet Web Template Editor to modify existing controls or add new ones. You can do so for any of the web templates of the applet without exiting IDE to select the next web template. You must access this editor through IDE.

If you select All Applications then the changes will reflect in all applications where this applet is in use. Select a web control and, with the mouse button depressed, move the selected web control to an unused placeholder then release the mouse button. In the Properties pane, modify the properties of the object as required. The Property pane displays the same properties as given in the Object List Editor. Select a control and, with the mouse button depressed, move the selected control to an unused placeholder then release the mouse button.

Using the Command Line to Validate Objects. Using the Command Line to Import an Archive. Previous Next JavaScript must be enabled to correctly display this content. Siebel Tools allows you to develop a single configuration that you can use to do the following: Deploy Siebel CRM across multiple types of clients Support multiple Siebel Business Applications and languages Upgrade Siebel product releases Maintain Siebel CRM Declarative configuration is a type of programming technique that uses objects and object properties in the Siebel repository to implement the logic that your business requires.

It might also be installed locally on your intranet or on a network location. Enabling Workspaces in the Development Environment In order to set up the Siebel development environment, the Siebel Administrator has to enable workspaces. For more information about: How to install Siebel Tools, see the Siebel Installation Guide for the operating system you are using. For information about Certifications, see article In the Development Tools Options dialog box, click the General tab.

Setting the Language Mode The language mode is a type of mode that allows you to configure Siebel CRM to display text in a language other than English. To set the language mode Make sure the repository includes the language data that Siebel Tools must show.

In Siebel Tools, click the View menu, and then click Options. For more information, see the Enabling Language Override section in this chapter. Click OK. Enabling Language Override A language override is a nontranslatable, locale property that you can configure differently for different locales. If the workspace is in Edit-In-Progress state, then the changes are tracked under the latest checked-out version.

Otherwise, a new version is created and changes are tracked under that new version until that version is checkpointed. If you edit the repository object again after it is checkpointed, the current version is incremented by 1 and all new changes are tracked under the current version until the new version is checkpointed. For more information on how to enable workspaces in Siebel Tools and then edit the repository objects, see Editing the Repository Objects.

For more information on how to configure non-workspace objects, see Configuring Non-Workspace Objects. You can delete the development workspaces that you own, but you cannot delete workspaces or parent workspaces that are owned by other users. In addition, development workspaces that are in the status of Submitted for Delivery or Delivered cannot be deleted from the repository. A list of available actions appears.

At the time you open the Workspace explorer pane, this pane lists all available workspaces that are in the database. After that, if other users use other workspace sessions to modify their workspaces in the same database, such as adding new workspaces or deleting the current ones, you need to refresh the Workspace explorer pane to display these changes. The Workspace explorer pane is refreshed displaying the latest changes for all workspaces in the database.

You can use the Modified Objects option under the Workspace menu to view the changes that you have made to objects in the current workspace. To see the list of modified objects in a workspace without opening a workspace, select that workspace and then select a version from the Workspace Version pane.

When you open a particular version, all versions succeeding the selected version are also opened. The Modified Objects pane lists the object names, object types, and operations that were performed for each modified object. The following table describes the values listed in the Operation column on the Modified Objects pane. Also indicates an operation of inserting, updating, or enabling the Inactive option for a child record. The checkpoint operation commits the changes that you made to the current workspace version of the selected workspace and sets that version to be non-editable.

After checkpointing the workspace, you are no longer able to make object changes to the current version of the workspace. All subsequent object changes will be tracked under the next version of the workspace. Enter the comments, which will be displayed in the Comment column on the Workspace Versions pane.

After a workspace version is check pointed, its status changes to Checkpointed in the My Workspaces pane and the Submit for Delivery option for that workspace is enabled under the Workspaces menu.

When the changes that were made since the last checkpointed version of the workspace cause issues, you can revert or roll back to the most recent checkpointed version.

You can also revert or roll back a checkpointed version to the previous checkpointed version. If you perform the revert process on a workspace with the status set to Edit-In-Progress or Checkpointed, then all changes that you made in the latest version are lost and the workspace reverts back to the last checkpointed version. If you perform the revert process on the first version of the workspace, then all changes that you made in the first version are lost and the status of the workspace reverts back to Created.

Rebasing merging a workspace is applying the changes that were made in the parent workspace as a result of deliveries by other workspaces that have branched off the same parent into the current workspace. You can perform the rebase process only after you perform the checkpoint operation at least on the first version of the workspace.

In the workspace dashboard, select the Workspace menu and then select the Rebase option. The Rebase Workspace dialog box displays the merge details and the rebase process bar in the Merge Status section. The status of the workspace in the View Mode pane is updated to Rebase-in-Progress and the version of the workspace is incremented by 1. If there is any conflict, the Rebase Workspace dialog box displays the Resolve Conflicts button and you must click this button to resolve the conflicts.

In the workspace dashboard, click the Finish button on the Merged Workspaces pane to complete the merge process. Alternatively, click the Cancel button on the Merged Workspaces pane to cancel the merge process. The workspace will be reverted to the last checkpointed version and its status is set to Checkpointed in the View Mode pane. After you click the Finish button, enter comments using the Enter Comment dialog box and click the OK button.

The status of the workspace in the View Mode pane is updated to Checkpointed. In the My Workspaces pane, the version of the workspace is incremented by 1 and the comments that you previously entered are also displayed. Workspace resolution is set to the From Version value by default. When you click the Finish button, the value of From Version is saved in your workspace.

If you select the Override option, then the workspace resolution changes to To Version and the value of To Version is saved in your workspace when you finish the rebase process. In a development environment where multiple users work in parallel making configuration changes concurrently in their own private workspaces, conflicts might arise when the same objects and attributes are modified by different users in their own private workspaces, and then the changes from these users are delivered to the main branch.

These situations often lead to non-trivial merges because of the conflicting changes between different users. For workspaces, the system detects the possibility of conflicts prior to workspace delivery. If conflicts or errors are found, the system displays the issues along with the default resolutions.

You must review the conflicts and apply the resolutions to resolve the issues. Identify the conflicts by viewing the conflict flags on the attributes. Notice that some conflicts must be explicitly resolved before you can submit the workspace for delivery again.

View the status message that describes the error or conflict in details for each object or attribute. If the system cannot resolve the conflict or the delivery process encounters an error while merging the changes, an error message appears. Although an attempt is made on all objects, the overall delivery process fails even if a single error is encountered.

The default resolutions for the attribute conflicts can be overridden by selecting the Override option. If you select the Override option by mistake, then you can clear it to resolve the issue.

Errors can happen on attributes when the merge process is unable to set the correct value. Common errors are when there are inconsistencies in the repository and a foreign key is missing. Object-level conflicts and errors, which are name conflicts, object inactive conflicts, and index violation errors.

A name conflict occurs when there are two different objects of the same type that have the same combination of name and parent ID. A potential violation of user key is detected as a result of the rebase operation, and the merge process selects a default resolution of renaming the object that belongs to the child workspace by appending the string -[Rebase].

Both object and name attribute are marked with a conflict flag in the Merge Conflicts dialog box. If a name conflict is not resolved, then subsequent delivery fails by identifying the system-generated name. This conflict cannot be resolved by selecting the Override option, but you must finish the rebase process and resolve it in either one of the two methods described in this example:.

User1 renames and creates a new business component with the name NewBC User2 cannot deliver his branch before starting a rebase process because this is a non-trivial merge. To resolve this conflict, both users can intend to either create two different objects or create the same object being duplicated, as in these cases:. Case Two logically different objects. Case The same object being duplicated. In this case, both users have duplicated the same record because they were not aware of the changes made by the other.

Subsequently, both users must perform the RevertObject operation or inactivate the NewBC[Rebase] business component. An object inactive conflict occurs when the target workspace being rebased has a change to an object that is inactivated in the source workspace.

Even if the source workspace has an inactive parent object, this conflict is still alerted to let users know that the change that is made in the workspace will not be applied at runtime because either this object or its parent is inactivated.

Users can either ignore this conflict or resolve this conflict by checking the Override option for the Inactive attribute. User2 modifies the account status Field by making it force active. He then tries to deliver this change to the MAIN workspace, but the system enforces a rebase.

On rebase, the merge process detects that the changes on the account status Field are no longer applied as the parent contact Business Component is inactivated.

Hence a conflict is logged against the contact Business Component and the corresponding inactive attribute. To resolve the conflict, users can select the Override option for the inactive attribute on the contact Business Component. An index violation error conflict occurs when there are two different objects of the same type having the same combination of contents.

A potential violation of the index is detected as a result of the rebase and the merge process cannot select any resolution.

Hence the system displays an error on the object and fails the rebase process. Users must fix this error either by manually modifying the fields involved in the index or by performing the RevertObject operation on the object on a single version or the entire workspace. This fix ensures that there is no longer a violation and then users can run the rebase process again. During the rebase process, the merge process detects the possibility of a unique key violation on the index involving the field Workflow Column Name Workflow Column Name, Workflow Object Name.

The object is marked with the key violation error in the Merge Conflicts dialog box. To resolve this conflict, User2 must perform either of the following resolutions to resolve the error and ensure that there is no longer an index violation, and then perform the rebase process again.

Case Modify the index-based fields. Case Run the RevertObject process. User2 runs the RevertObject process on the AnotherCompCol object either for a single version or for all versions in the workspace. In the workspace dashboard, select the Workspace menu and then select the Merge Reports option.

The Merged Workspaces section displays the status of merge, resultant version, base version, From version, and To version of the merge process.

The Object Differences section displays the object name, object type, top-level parent name and type, and the status of the selected object after the merge process is completed. The Attribute Differences - Critical Conflicts section displays the attribute information including the workspace resolution, base version value, To and From version values, conflict, override, and so on. After you perform the checkpoint process on the latest workspace version, you can use the Submit for Delivery option under the Workspace menu to deliver the changes of your workspace to the MAIN workspace.

The Submit for Delivery process initiates the governance flow that may require one or more levels of review and approval. After the changes are submitted for delivery, the workspace is locked or made read-only to prevent further configuration changes while the workspace is being reviewed.

After the workspace is approved, it is delivered into the MAIN workspace. In the workspace dashboard, select the Workspace menu and then select the Submit for Delivery option.

The workspace status in the View Mode pane changes to Submitted for Delivery and the workspace title indicates the workspace is read-only. You cannot perform any operation on the objects in the Object Explorer pane.

Except for the Deliver option, other options under the Workspace menu such as Checkpoint, Revert, and Rebase are also disabled. Alternatively, click the No button to cancel the submission. Then you can continue to make changes on the objects. If there is a non-trivial merge issue, then an error message appears and you must perform the rebase process and then submit the workspace for delivery again. Before delivering a workspace, workspace administrators must change the status of that workspace to Submitted for Delivery to make it ready for the delivery process.

After the status of the workspace is changed to Submitted for Delivery, it is a read-only workspace and end users or developers cannot perform any other repository changes on it until the merging process is completed. Any repository changes to that workspace would make the delivery process fail. To cancel the workspace delivery process, avoid the delivery failures, and allow end users or developers to be able to make repository changes on the workspaces with the status of Submitted for Delivery, workspace administrators must revert the status of that workspace back to Checkpointed and Editable by using the Undo Submit for Delivery option under the Workspace menu or running the UndoSubmitForDelivery command from the Command Prompt window.

Delivering a workspace, or merging workspace changes, is applying the changes that are made in the workspace into its parent workspace such as the MAIN workspace or the root workspace.

You must always perform the workspace delivery process to the immediate parent workspace. You cannot deliver the workspace to any arbitrary workspace. If you are the owner of the parent workspace or if you are a workspace administrator who is also the owner of the parent workspace, then you can run the workspace delivery process.

For more information on how to deliver workspaces, see Delivering Workspaces. You can export all workspace objects to an archive file, such as object definitions of the object types Business Component, Applet, View, Screen, Integration Object, Business Object, and so on.

The Export Workspace to Archive dialog box appears. By default, the Workspace To Version field always displays the latest version of the workspace. The Export to Archive File dialog box appears. The status bar in this dialog box indicates the child objects that are included in the export process. When the process finishes, this dialog box displays the top-level objects in the Objects to Archive list. You can use the Compare option under the Workspace menu to identify the changes that are made to the objects in two selected workspace versions.

In the workspace dashboard, select the Workspace menu and then select the Compare option. The Compare Workspace dialog box appears. In the First Selection group box, the value in the Workspace Name field is populated using the value of the opened workspace name and the Version field is populated using the value of the opened version of that workspace. The status bar indicates that the process is running. When the process finishes, the Compare Objects dialog box appears, displaying all top-level objects that have differences in the two selected workspace versions.

The Compare Objects dialog box displays the object properties, including the similarities and the differences for each attribute. A workspace administrator who is also the owner of the MAIN workspace root, parent, or master workspace can perform the process of flattening workspace versions using the command prompt.

No other users can perform this process. When you access Siebel Tools after the flattening workspace version process has successfully completed:. Siebel Tools is opened in the non-workspace mode as in the previous releases of Siebel Tools. For more information on how to flatten workspace versions, see Flattening Workspace Versions. Only one single public version of the object is available for all users.

Hence, configuration on instances of this object is centrally controlled by the workspace administrator, who can lock all relevant projects and objects. Developers are able to configure the respective objects or projects after their requests to release the locks on these objects or projects are granted by the workspace administrator. For more information on how to control the access on non-workspace objects, see Controlling Access on Non-Workspace Objects.

In Siebel Tools Innovation Pack , workflow objects were considered non-workspace objects. However, workflow objects are also workspace objects in Siebel Tools Innovation Pack and the later releases. This section describes how to use Siebel workflows in Siebel workspaces. Using Workflows in Workspaces Overview. Creating New Workflows.

Modifying Existing Workflows. Importing Workflows into Workspaces. Exporting Workflows from Workspaces. Validating Workflows. Debugging Workflows. Invoking Workflows. Delivering Workspaces that Use Workflows. The statuses of all workflows are always In Progress by default. Hence the Status column of the workflows is no longer required and not available in Siebel Tools starting with Siebel Tools Innovation Pack If you are a developer who is not the owner of the root workspace, you cannot activate a workflow but you can publish the workflow.

When you click the Publish button in the Workflow Task Editor toolbar, the system moves the workflow to the Completed state.

If you are a developer who is also the owner of the root workspace, you can publish and activate the workflow. As you activate the workflow, the version number is incremented.

The version changes can be viewed in the thin or thick client platform, but the version number always remains 0 zero in Siebel Tools. Only the Siebel system Administrator can activate the Workflows feature by either of the following actions:. Other workflow users can search for the workflows that need to be activated and then click the Activate button on the retrieved records to activate the workflows.

For more information on how to create a new developer workspace, see Creating New Workspaces. For more information on how to open an existing developer workspace, see Opening Existing Workspaces. Select the workflow that you want to modify, right-click, and select the Edit Workflow Process option. In Siebel Tools, to create a new workspace, select the Workspace menu, select the Create menu option, enter all required values, and click the OK button.

From the list of all available workflows, select the workflow that you want import into the current developer workspace. You can use the Export Workflow Process option under the Workflow Object List to export a workflow from a workspace to a defined location. Select the workflow to export, right-click, and select the Export Workflow Process option.

In the Workflow Process List, select the workflow to validate, right-click, and select the Validate option. The Validate wizard opens. If there are any errors in the workflow, the wizard displays the error information and the location of the log file. For more information on how to fix the conflict errors and apply resolutions, see Detecting Conflicts in Workspaces and Applying Resolutions. Alternatively, click the Cancel button to cancel the Validating Workflow process and return to the Siebel Tools window.

Siebel Tools launches the thick client with the user-provided database details to simulate the workflow wizard. You can use the Debug tab under the Development Tools Options window to debug workflows.

Under the Run-time start up information and Login Information sections, enter the following required information:. In the Workflow Process List, select a workflow to simulate, right-click your mouse, and select the Simulate Workflow Process option. The Watch window appears showing the values of workflow properties at each simulating step. For a detailed example that uses the Watch window, see information about defining a workflow process that closes obsolete service requests in Siebel Business Process Framework: Workflow Guide.

Performing the Deliver Workspace process does not activate the workflow. For the detailed information on how to deliver workspaces, see Delivering Workspaces. This topic describes how to perform Workspace administrative tasks in Siebel Tools. These tasks are performed only by the users who are assigned the user role Workspace Administrator.

Editing the Repository Objects. Controlling Access on Non-Workspace Objects. Publishing Tables. Using Workspaces for Seed Data. Adding the Workspace Prefix in System Preferences. This topic discusses how to enable the workspaces in Siebel Tools and edit the repository objects. By default, the MAIN workspace or the last-modified workspace opens at the last-updated session.

To create a new workspace, select the Workspace menu, select the Create menu option, enter all required values, and click the OK button. To modify an existing workspace, select a workspace in the Workspace Explorer pane, right-click and select the Open option. Perform the Checkpoint process to check the changes that you just made by selecting the Workspace menu bar and the Checkpoint option. After all changes are checked, run the Rebase process with the parent workspace by selecting the Workspace menu bar and the Rebase option.

Optionally, override the values in the To Version Value list and select the Override option. For more information on how to edit workspace-enabled repository objects, see Editing Workspace-Enabled Repository Objects. For more information on how to enable the workspaces in Web Tools and edit the repository objects, see Enabling Workspaces in Web Tools and Editing the Repository Objects. Any repository change to that workspace would make the delivery process fail.

Click the Yes button to revert the status of the workspace from Submitted for Delivery to Checkpointed and Editable. Open the Command Prompt window from your computer by clicking the Start button and then selecting the Run option. After the status of the workspace is reverted, end users and developers of that workspace must perform these steps before they can make any repository change on it:.

In the View Mode pane, confirm that the reverted workspace status is now Checkpointed and the title of the workspace includes Editable. You cannot deliver workspace to any arbitrary workspace.

If you are the owner of the parent workspace or if you are a workspace administrator who is also the owner of the parent workspace, then you can use one of these options to run the workspace delivery process:. Only workspace administrators can optionally enter comments into the command line while running the Deliver command from the Command Prompt window.

If you are a workspace administrator without being the owner of the parent workspace, you can run the workspace delivery process by running the Deliver command from the Command Prompt window. A workspace can be delivered once. Workspace administrators have full permissions on the MAIN workspace, including delivering the workspace. However, end users and developers have read-only access on the MAIN workspace.

On the Siebel Tools workspace dashboard, confirm that the status of the workspace is Submitted for Delivery. We know it can be difficult to keep up with everything going on and what it could mean for your business. The biggest fundamental change happening in the Siebel world is the Cloud Native project from Oracle. At a high level, kubernetes and dockers are being introduced to supercharge the agility of the platform. Traditionally, adding extra capacity and managing servers could be a major challenge with many variables at play.

The premise of Cloud Native means this will be far easier in the future and companies can scale up cost-effectively. This infrastructure will support microservices in the coming years that gives Siebel owners more flexibility than ever before. This reduces the risks of single points of failure and creates smaller applications with optimized features.

We believe in the long term, this will allow Oracle to effectively reach customers with the best features for their specific needs. Capabilities will be added throughout the year to allow companies to increase the differentiation between their desktop and mobile versions. Making use of Oracle JET will speed up the development of the mobile form in particular. This is crucial as the use cases when accessing the same data through different devices need to be adapted to empower the users.

REST APIs have been enabled for some time but the offering has matured and we are seeing more examples of smooth implementations. We expect a greater take up of people using REST calls in this way to enhance other interfaces.