Abstract: Some implementations of the disclosed systems, apparatus, methods and computer program products provide for shipping management of serialized products. In various embodiments, a product transfer record may be created to track the movement of a group of serialized items of a product from one location to another. A product transfer state may be provided for each of the serialized products within the transfer record. The product transfer state may then be updated to match the status of the transfer of the serialized item.

Abstract: A request to contact a service provider may be received from a client machine. The request may be associated with an identity claim and including a service identifier. The identity claim may be validated via a distributed identity service that includes a plurality of identity nodes in communication via a network. Validating the identity claim may include determining a designated network identifier associated with a distributed identity account shared among the plurality of identity nodes. A service query that includes the service identifier and the designated network identifier may be sent to a plurality of customer relations management services. A communication session may be established between a service provider remote computing system and the client machine. The service provider may store customer relations management information at a designated one of the plurality of customer relations management services.

Abstract: A request to present digital content at a client machine associated with a designated network identifier may be received. For each of a plurality of preference characteristics, a respective characteristic query message may be transmitted via a network to a respective plurality of identity nodes via a gossip communication protocol defining a peer-to-peer procedure for transmitting information among the plurality of identity nodes. For each of the plurality of preference characteristics, a respective preference identification response message that includes a respective preference value corresponding with the respective preference characteristic may be received. The designated network identifier may be stored in a trust ledger shared among the plurality of identity nodes. A digital content item may be selected based at least in part on the preference values.

Abstract: An interaction message may be received as part of a digital interaction between the database system and a remote computing device. A public trust ledger identifier associated with the interaction message may be determined. A non-fungible preference token recorded in a public trust ledger within a wallet owned by the public trust ledger identifier may be identified. The non-fungible preference token may include one or more preference values identifying preference information for a user associated with the public trust ledger identifier. An updated preference value based at least in part on the digital interaction. An instruction to update the non-fungible preference token to include the updated preference value may be sent to the public trust ledger.

Abstract: Methods, systems, and devices supporting a data model abstraction framework are described. Some platforms (e.g., a multi-tenant cloud computing platform) may manage data across a number of persistent systems (e.g., cloud platforms, data stores, packages, etc.). To efficiently manage data across such systems, a platform may implement a metadata-driven abstraction layer. The abstraction layer may support a number of interface objects and interface fields, which may operate as abstracted versions of persistent objects and persistent fields. External entities (e.g., users, triggers, customizations, packages, plugins, or any other entities) may interact with the interface objects, and the abstraction layer may automatically handle mappings from the interface objects to the persistent systems. By using the metadata-driven abstraction layer, the platform may resolve conflicts between the external entities and multiple underlying persistent systems.

Abstract: Described herein are means for implementing consensus on read via a consensus on write smart contract trigger for a Distributed Ledger Technology (DLT) platform in conjunction with a cloud based computing environment.

Abstract: A first message indicating that a first digital token created within an on-demand database system and recorded in a public trust ledger external to the on-demand database system has been transferred from a first party within the public trust ledger to a second party within the public trust ledger may be received. The on-demand database system may communicate with the public trust ledger to add a wallet account as a secondary owner to a smart contract that includes a second digital token. The smart contract may identify one or more conditions for transferring the second digital token to the second party. A second message identifying the second digital token may be transmitted to the second party within the public trust ledger.

Abstract: A request to perform an action related to a smart contract recorded on a public trust ledger external to the database system may be received via a communication interface at a database system. The request may authenticate a designated database system account. A determination may be made as to whether the designated database system account is authorized to perform the action by accessing definition information for a public trust ledger synthetic party identifying a plurality of database system accounts authorized to perform one or more actions related to the smart contract. The database system may communicate with a token exchange to perform the action by executing the smart contract when it is determined that the designated database system account is authorized to perform the action.

Abstract: A request to exchange of a first quantity of a first fungible digital token type stored within a smart contract instance recorded in a public trust ledger and owned by a first party within the public trust ledger may be received via a communication interface at a database system. The request may authenticate a first account in the database system. The first account may be linked with the first party within the public trust ledger. The smart contract instance may be executed to determine whether the requested exchange is permissible based on one or more transaction rules included within the smart contract instance. The database system may be updated to reflect a transaction recorded within the public trust ledger when it is determined that the requested exchange is permissible.

Abstract: Systems, methods, and apparatuses for implementing super community and community sidechains with consent management for distributed ledger technologies in a cloud based computing environment are described herein.

Abstract: Techniques and mechanisms described herein relate to a database system. A digital asset referenced in one or more database tables within an on-demand database system accessible to a plurality of entities may be identified. The digital asset may be owned by a first one of the plurality of entities. A smart contract that includes a token identifying the digital asset may be generated. The smart contract may be recorded within a distributed trust ledger. The token may be owned by a first account within the distributed trust ledger. The on-demand database system may include a correspondence linking the first entity with the first account. The on-demand database system may be updated to include a reference linking the digital asset with the token.

Abstract: A request may be received to access a digital asset uniquely identified by an identifier within an on-demand database system configured to provide computing services to a plurality of entities via the internet. Ownership of the digital asset may be determined based on ownership of a designated smart contract recorded in a public trust ledger. A plurality of related smart contracts recorded in the public trust ledger may be identified. Each of the related smart contracts may be linked with the designated smart contract. Two or more of the smart contracts may each include a respective one or more non-fungible tokens related to the digital asset. A respective state for two or more of a plurality of modifiable values may be determined. Each of the modifiable values may be being stored within a respective one of the plurality of related smart contracts within the public trust ledger.

Abstract: A request may be received to transfer from a first entity to a second entity a right related to a digital asset stored in an on-demand database system. The on-demand database system may provide computing services to a plurality of entities via the internet. A token associated with the digital asset may be identified. The token may being included in a smart contract recorded within a distributed trust ledger and may be owned by a first distributed trust ledger account. The smart contract may be executed within the distributed trust ledger to record a transfer of the token from the first distributed trust ledger account to a second distributed trust ledger account. The on-demand database system may be updated to include one or more database entries reflecting the recorded transfer.

Abstract: A request may be received to access a digital asset uniquely identified by an identifier within an on-demand database system configured to provide computing services to a plurality of entities via the internet. Ownership of the digital asset may be determined based on ownership of a designated smart contract recorded in a public trust ledger. A plurality of related smart contracts recorded in the public trust ledger may be identified. Each of the related smart contracts may be linked with the designated smart contract. Two or more of the smart contracts may each include a respective one or more non-fungible tokens related to the digital asset. A respective state for two or more of a plurality of modifiable values may be determined. Each of the modifiable values may be being stored within a respective one of the plurality of related smart contracts within the public trust ledger.

Abstract: Systems, methods, and apparatuses for implementing commerce rewards across tenants for commerce cloud customers utilizing blockchain technologies in conjunction with a cloud based computing environment are described herein.

Abstract: Providing expert help to a user comprises providing an application for execution on a mobile device of the user associated with an entity. A computer receives entity rules from the entity, the entity rules include a definition of how communication channels are created. The entity rules are stored in a rules database in association with the user. A help request initiated by the user through the application program and sent by the mobile device, the help request comprising a current context of the user comprising a user ID and a task ID of a current task. Using the entity rules, the current context is transformed into search parameters that are used to search a knowledge repository for experts having profiles that match the current context of the user. The entity rules are used to automatically create a communication channel between the user and the experts matching the current context.

Abstract: Systems, methods, and apparatuses for implementing certificates of authenticity of digital twins transacted onto a blockchain using Distributed Ledger Technology (DLT) in conjunction with a cloud based computing environment are described herein.

Abstract: A method performed by a system of a host organization for providing access controls for data a blockchain, the system providing a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization each serving as nodes in a blockchain network. The method includes receiving a request including an identifier of a requestor, the request to access transaction data having defined privileges, requesting access to the transaction data from nodes in the blockchain network, a request for access including the identifier of the requestor, receiving at least one shared secret from an owner node in the blockchain network indicating consensus to access the transaction data by the requestor, and denying access to the transaction data in response to receiving insufficient shared secrets from the nodes indicating the requestor does not meet requirements of the defined privileges of the transaction data.

Abstract: Disclosed herein are system, method, and computer program product embodiments for processing a written-language contract using an industry-specific natural language processing model to determine flows or actions to undertake in a Customer Relationship Management (CRM) solution. A CRM solution may include the ability to receive or create a binding natural-language contract. The CPQ or CRM system may use natural language processing (NLP) to determine terms and conditions included in a natural-language contract. The NLP may further use an industry-specific model that may be determined based on information in the CRM solution to more efficiently and accurately analyze the natural-language contract. The CRM solution may further receive a legal language construct and convert the terms of the legal language construct into a smart contract.

Abstract: Systems, methods, and apparatuses for implementing super community and community sidechains with consent management for distributed ledger technologies in a cloud based computing environment are described herein.