Abstract: Techniques are disclosed relating to installing and operating applications in a server-based application workspace. A computer system, while operating the server-based application workspace, may store subscription information indicating a user that is a developer for a particular application package, and one or more users that are subscribers for the particular application package. The computer system may further store lock data for the particular application package that indicates user permissions to edit at least one application component for the particular application package. Based on the lock data, the computer system may permit the developer to edit the at least one application component of the particular application package, and deny requests from the one or more users to edit the at least one application component.

Abstract: Techniques are disclosed relating to installing and operating applications in a server-based application workspace. A computer system, while operating the server-based application workspace, may store subscription information indicating a user that is a developer for a particular application package, and one or more users that are subscribers for the particular application package. The computer system may further store lock data for the particular application package that indicates user permissions to edit at least one application component for the particular application package. Based on the lock data, the computer system may permit the developer to edit the at least one application component of the particular application package, and deny requests from the one or more users to edit the at least one application component.

Abstract: Techniques are disclosed relating to installing and operating applications in a server-based application workspace. A computer system, while operating the server-based application workspace, may store subscription information indicating a user that is a developer for a particular application package, and one or more users that are subscribers for the particular application package. The computer system may further store lock data for the particular application package that indicates user permissions to edit at least one application component for the particular application package. Based on the lock data, the computer system may permit the developer to edit the at least one application component of the particular application package, and deny requests from the one or more users to edit the at least one application component.

Abstract: A system and method for protecting access to metadata based on package membership. The system creates at least one customized metadata type for a first software package and assigns a package protected access mode to control access to the at least one customized metadata type by respective components of one or more software packages. The system denies access to the at least one customized metadata type, according to the package protected access mode, by at least one component of a second software package that shares a namespace with the first software package.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: A system and method for protecting access to metadata based on package membership. The system creates at least one customized metadata type for a first software package and assigns a package protected access mode to control access to the at least one customized metadata type by respective components of one or more software packages. The system denies access to the at least one customized metadata type, according to the package protected access mode, by at least one component of a second software package that shares a namespace with the first software package.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: In accordance with disclosed embodiments, there are provided systems, methods, and apparatuses for implementing field types which are defined via custom metadata types within a computing environment.

Abstract: Techniques are disclosed relating to installing and operating applications in a server-based application workspace. A computer system, while operating the server-based application workspace, may store subscription information indicating a user that is a developer for a particular application package, and one or more users that are subscribers for the particular application package. The computer system may further store lock data for the particular application package that indicates user permissions to edit at least one application component for the particular application package. Based on the lock data, the computer system may permit the developer to edit the at least one application component of the particular application package, and deny requests from the one or more users to edit the at least one application component.

Abstract: Architectures and Techniques for Record Protection and Field Management. A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.

Abstract: A database system that supports associating a custom metadata type with loosely coupled triggers may be implemented to include instructions to receive a definition of a custom metadata type, the definition comprising at least one relationship field associated with a triggerable database object. The database system may also include instructions to associate the definition of the custom metadata type with a loosely-coupled trigger, and to cause the loosely-coupled trigger to execute based on generating a custom metadata record of the custom metadata type. The custom metadata record including a triggerable database object value for the relationship field.

Abstract: In accordance with disclosed embodiments, there are provided systems, methods, and apparatuses for implementing field types which are defined via custom metadata types within a computing environment.

Abstract: Architectures and Techniques for Record Protection and Field Management. A software package having one or more custom metadata types is installed. The software package has computer-executable code that causes one or more processors to perform at least accessing the one or more custom metadata types. One or more protected records are accessed within the one or more custom metadata types. For the protected records, code in the installed package can read the protected records and can return the records whether protected or not. If the custom metadata types are in a separate base package, code in the base package can also read the records. Returned information is stored in the one or more custom metadata records that has been accessed.

Abstract: A database program includes loose triggers that are not coupled to specific entities at the time the database program is compiled. The database program provides a user interface that allows a user to couple selected entities to the loose triggers or decouple selected entities from loose triggers. The database program validates the entities that are selected by the user for coupling or decoupling and stores the coupled entities as part of the loose trigger definitions in a loose trigger metadata database.

Abstract: A database system that supports associating a custom metadata type with loosely coupled triggers may be implemented to include instructions to receive a definition of a custom metadata type, the definition comprising at least one relationship field associated with a triggerable database object. The database system may also include instructions to associate the definition of the custom metadata type with a loosely-coupled trigger, and to cause the loosely-coupled trigger to execute based on generating a custom metadata record of the custom metadata type. The custom metadata record including a triggerable database object value for the relationship field.