Abstract: In accordance with embodiments, there are provided techniques for managing functionality changes of a database platform of a service provider. The techniques facilitate implementing changes to the database platform while minimizing work flow reductions to users of the database platform. To that end, one embodiment of the present invention delays implementation of the changes for a duration of time to provide users of the database platform an opportunity to adjust behavioral interaction with the database platform. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the users may be afforded an opportunity to selectively enable and disable the functionality changes before the duration of time expires.

Abstract: In accordance with embodiments, there are provided techniques for managing functionality changes of a database platform of a service provider. The techniques facilitate implementing changes to the database platform while minimizing work flow reductions to users of the database platform. To that end, one embodiment of the present invention delays implementation of the changes for a duration of time to provide users of the database platform an opportunity to adjust behavioral interaction with the database platform. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the users may be afforded an opportunity to selectively enable and disable the functionality changes before the duration of time expires.

Abstract: In accordance with embodiments, there are provided techniques for managing functionality changes of an on-demand database system. The techniques facilitate implementing changes to the database system while minimizing work flow reductions to users of the database system. To that end, one embodiment of the present invention delays implementation of the changes to provide users of the system an opportunity to adjust behavioral interaction with the database. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the user may be afforded an opportunity to selectively enable and disable the functionality changes before the duration expires.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for interacting with a process diagram. These mechanisms and methods for interacting with a process diagram may allow for a user's enhanced interactive experience with the process diagram. The ability of embodiments to provide such enhancements may allow for improved navigation of the process diagram, searching of the process diagram, editing of the process diagram, etc.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for interacting with a process diagram. These mechanisms and methods for interacting with a process diagram may allow for a user's enhanced interactive experience with the process diagram. The ability of embodiments to provide such enhancements may allow for improved navigation of the process diagram, searching of the process diagram, editing of the process diagram, etc.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for interacting with a process diagram. These mechanisms and methods for interacting with a process diagram may allow for a user's enhanced interactive experience with the process diagram. The ability of embodiments to provide such enhancements may allow for improved navigation of the process diagram, searching of the process diagram, editing of the process diagram, etc.

Abstract: Methods and systems include embodiments that recursively save parent, grandparent, and other records in a database that depend from a record. User-provided code within a save event or trigger can thus call further save methods without corrupting the database. Junction objects, objects that reflect records with two or more parents, can also be recursively saved.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for rule-based performance of actions on related objects. These mechanisms and methods for rule-based performance of actions on related objects can provide a generalized technique for configuring related object actions that are responsive to object updates. The ability to provide this generalized technique can enable actions to be automatically performed on objects in response to updates to related objects, in a rule-based manner.

Abstract: Methods and systems include embodiments that recursively save parent, grandparent, and other records in a database that depend from a record. User-provided code within a save event or trigger can thus call further save methods without corrupting the database. Junction objects, objects that reflect records with two or more parents, can also be recursively saved.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for recalling execution of an approval process on a data object. These mechanisms and methods for recalling execution of an approval process on a data object can enable actions to be automatically performed in association with the recall of the execution of the approval process on the data object. Thus, manual initiation of actions associated with a recall may be avoided.

Abstract: Methods and systems include embodiments that recursively save parent, grandparent, and other records in a database that depend from a record. User-provided code within a save event or trigger can thus call further save methods without corrupting the database. Junction objects, objects that reflect records with two or more parents, can also be recursively saved.

Abstract: In accordance with embodiments, steps in a multi-tenant database service are approved to manually and/or automatically satisfy requests to approve various steps in the service. The ability of embodiments to provide such additional approval capabilities may lead to more flexible step approval during use of the on-demand database service.

Abstract: A computer implemented method a document management workflow in a multi-tenant system environment is disclosed. The method includes receiving instructions to create a composition a document. The document is encapsulated in a knowledge article version and the knowledge article version having a document category. The knowledge article version is associated with a knowledge article. The method further includes invoking the document management workflow that is specific to the knowledge article, the knowledge article version and the document category and configuring the document management workflow to include a plurality of workflow steps based on the knowledge article, the knowledge article version and the document category. Each of the plurality of workflow steps are then associated with one or more triggers and actor roles. The actor roles define permissible actions in each of the plurality of workflow steps.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for rule-based performance of actions on related objects. These mechanisms and methods for rule-based performance of actions on related objects can provide a generalized technique for configuring related object actions that are responsive to object updates. The ability to provide this generalized technique can enable actions to be automatically performed on objects in response to updates to related objects, in a rule-based manner.

Abstract: In accordance with embodiments, there are provided techniques for managing functionality changes of an on-demand database system. The techniques facilitate implementing changes to the database system while minimize work flow reductions to users of the database system. To that end, one embodiment of the present invention delays implementation of the changes to provide users of the system an opportunity to adjust behavioral interaction with the database. In accordance with another embodiment of the present invention, users may implement the functional changes to determine any adverse impact on work flow, before the functional changes become permanent. In another embodiment, the user may be afforded an opportunity to selectively enable and disable the functionality changes before the duration expires.

Abstract: Methods and systems include embodiments that recursively save parent, grandparent, and other records in a database that depend from a record. User-provided code within a save event or trigger can thus call further save methods without corrupting the database. Junction objects, objects that reflect records with two or more parents, can also be recursively saved.