Org sync async subscribe emails

A method, comprising:

• providing, for presentation on a display of a user device of a second entity, publish metadata indicating a first set of object types, the publish metadata indicating data items stored in at least one database of a first entity and available via subscription from the first entity;
• processing, by the second entity, an indication of user input submitted at the user device, the user input selecting subscription metadata, the subscription metadata indicating at least a subset of the first set of object types;
• transmitting, by the second entity to the first entity, a request pertaining to a data subscription between the first entity and the second entity;
• updating, by the second entity, a second transaction state to indicate that a subscription is in progress, wherein the subscription metadata cannot be modified while the second transaction state indicates that a subscription is in progress;
• and
• after updating the second transaction state and transmitting the request, initiating a subscription process to provide the subscription metadata to the first entity.

A computer program product comprising computer-readable program code capable of being executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code comprising instructions configurable to cause:

• providing publish metadata by a first entity, the publish metadata indicating a first set of object types, the publish metadata indicating a plurality of data items stored in at least one database of the first entity and available via subscription from the first entity by a second entity;
• processing, by the first entity, a request received from the second entity, the request pertaining to a data subscription between the first entity and the second entity;
• responsive to processing the request, updating, by the first entity, a first transaction state to indicate that a subscription is in progress, wherein the publish metadata cannot be modified while the first transaction state indicates that a subscription is in progress;
• and
• after updating the first transaction state to indicate that a subscription is in progress, participating in a subscription process such that subscription metadata is received by the first entity from the second entity and stored in a database by the first entity, the subscription metadata indicating at least a subset of the first set of object types.

A system comprising:

• a database system implemented using a server system, the database system configurable to cause:
• providing publish metadata by a first entity, the publish metadata indicating a first set of object types, the publish metadata indicating a plurality of data items stored in at least one database of the first entity and available via subscription from the first entity by a second entity;
• processing, by the first entity, a request received from the second entity, the request pertaining to a data subscription between the first entity and the second entity;
• responsive to processing the request, updating, by the first entity, a first transaction state to indicate that a subscription is in progress, wherein the publish metadata cannot be modified while the first transaction state indicates that a subscription is in progress;
• and
• after updating the first transaction state to indicate that a subscription is in progress, participating in a subscription process such that subscription metadata is received by the first entity from the second entity and stored in a database by the first entity, the subscription metadata indicating at least a subset of the first set of object types.