From f0fd392703869c1e9e60f2d57d83ffc784462a29 Mon Sep 17 00:00:00 2001 From: Max Kuzkin Date: Fri, 18 Mar 2022 01:24:36 -0700 Subject: [PATCH] removing redundant sections from the object description files + minor corrections in the URLs that were pointing to staging --- agreement-versions/object.md | 19 ++---------- cases/object.md | 19 ++---------- distribution-contracts/object.md | 22 ++----------- items/object.md | 18 ++--------- listings-request/object.md | 21 ++----------- listings/object.md | 19 ++---------- offers/object.md | 22 ++----------- partners/object.md | 18 ++--------- price-lists/object.md | 24 ++------------- products/object.md | 18 ++--------- program-contracts/object.md | 20 ++---------- report-repositories/object.md | 22 ++----------- report-schedules/object.md | 20 ++---------- reports/object.md | 18 ++--------- service-contracts/object.md | 20 ++---------- subscriptions-fulfillment-request/object.md | 34 ++------------------- subscriptions/object.md | 27 ++-------------- syndication-contracts/object.md | 19 ++---------- tier-account-requests/object.md | 20 ++---------- tier-accounts/object.md | 15 ++------- tier-config-request/object.md | 32 ++----------------- tier-config/object.md | 20 ++---------- usage-files/object.md | 33 ++------------------ usage-records/object.md | 27 ++-------------- users/object.md | 18 ++--------- 25 files changed, 50 insertions(+), 495 deletions(-) diff --git a/agreement-versions/object.md b/agreement-versions/object.md index 78bf0e9..8f7085f 100644 --- a/agreement-versions/object.md +++ b/agreement-versions/object.md @@ -3,20 +3,5 @@ Agreements represent versioned templates that are created by Distributors to sign corresponding Contracts with other accounts (Vendors or Resellers). Therefore, Distributors are required to generate an agreement before creating contracts on the CloudBlue Connect platform. There are several types of agreements on the CloudBlue Connect platform. This includes program agreements, distribution agreements, service agreements, referral agreements, and syndication agreements. Consequently, each agreement is used to collaborate with Vendors, invited Distributors, or Resellers and serves as a template for corresponding contract type. Agreement objects also feature agreement versions. Agreement versions, as the name implies, represent various versions (i.e., different document versions) of your agreement. Note that agreement objects don't include statuses or transitions. However, the system provides a specific workflow for agreement versions. Thus, for example, the Connect platform enables Distributors to create agreement versions in the *Active* or *Inactive* state. In case certain criteria are met, your agreement version can be activated, deactivated or deleted. Access required statuses and transitions for further description details. -## Available Statuses -The following list displays available statuses of the agreement version objects on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Active](s-a-active.html) -* B. [Inactive](s-b-inactive.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [New Active Agreement Version Creation](t-1-new-active.html) -2. [New Inactive Agreement Version Creation](t-2-new-inactive.html) -3. [Agreement Version Deactivation](t-3-act-inactive.html) -4. [Agreement Version Reactivation](t-4-inact-active.html) -5. [Active Agreement Version Removal](t-5-act-deleted.html) -6. [Inactive Agreement Version Removal](t-6-inact-deleted.html) - -## Learn more -In case more information on agreement objects or agreement types is required, refer to the [Partners module documentation](https://connect.cloudblue.com/community/modules/partners/agreements/) from the Connect Community page. +## Additional Information +Please refer to the [Partners module documentation](https://connect.cloudblue.com/community/modules/partners/agreements/) for more information. diff --git a/cases/object.md b/cases/object.md index d0034f8..0040c16 100644 --- a/cases/object.md +++ b/cases/object.md @@ -5,21 +5,6 @@ Once a new Case is created, the system assigns the *Pending* status to this Case Therefore, the system assigns the *Inquiring* status to this Case. Partners can also transfer the case back to the *Pending* state if all required information is presented. Partners can also assign the *Resolved* status to their pending Case if necessary. Thus, this Case will be resolved and the system automatically assigns the *Closed* status to it (depending on your specified [Autoclose Timeout](https://connect.cloudblue.com/community/modules/account/single-sign-on/azure-active-directory/) setting within the **Account** module). Note that the system also allows closing resolved Cases manually or reopen resolved Cased and transfer them back to the *Pending* state. -## Available statuses -The following provides a list of all available case states on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: -* A. [Pending](s-a-pending.html) -* B. [Inquiring](s-b-inquiring.html) -* C. [Resolved](s-c-resolved.html) -* D. [Closed](s-d-closed.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [New Case Creation](t-1-new-pending.html) -2. [Data Inquiry](t-2-pend-inquiring.html) -3. [Inquired Data is Submitted](t-3-inq-pending.html) -4. [Case Resolution](t-4-pend-resolved.html) -5. [Case Closure](t-5-res-closed.html) -6. [Case Reopening][t-6-res-pending.html] -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/helpdesk/) for more information. +## Additional Information +Please refer to the [Helpdesk module](https://connect.cloudblue.com/community/modules/helpdesk/) documenation for more information. \ No newline at end of file diff --git a/distribution-contracts/object.md b/distribution-contracts/object.md index e004b15..04e69ca 100644 --- a/distribution-contracts/object.md +++ b/distribution-contracts/object.md @@ -5,23 +5,5 @@ Vendors should enroll a distribution agreement to create and enroll a distributi Furthermore, Distributors can refine provided data and transfer the pending contract back to the *Enrolling* state. Distributors can also terminate activated contracts. In case the **Auto Accept** option from the **distribution agreement details screen** is enabled, the state flow of distribution contracts is different. Namely, Vendors don't need to enroll automatically generated distribution contracts and Distributors are not required to approve or reject these contracts. However, Distributors can still terminate the active contracts. -## Contract Statuses -The following list displays available distribution contract statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: - -* A. [Enrolling](s-a-enrolling.html) -* B. [Pending](s-b-pending.html) -* C. [Active](s-c-active.html) -* D. [Rejected](s-d-rejected.html) -* E. [Terminated](s-e-terminated.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Contract Enrollment](t-1-new-enrolling.html) -2. [Enrolling to Pending Contract Conversion](t-2-enr-pending.html) -3. [Contract Activation](t-3-pen-active.html) -4. [Contract Rejection](t-4-pen-rejected.html) -5. [Contract Termination](t-5-act-terminated.html) -6. [Data Refinement](t-6-pen-enrolling.html) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/partners/contracts/distribution-contracts/) for more information. +## Additional Information +Please refer to the [Partners Management module](https://connect.cloudblue.com/community/modules/partners/contracts/distribution-contracts/) documentation for more information. diff --git a/items/object.md b/items/object.md index 7ff652d..044b7a1 100644 --- a/items/object.md +++ b/items/object.md @@ -4,19 +4,5 @@ Items are individual resources or units (such as a license or any other SKU) tha Pay-As-You-Go items are used by Vendors to implement a system that based on the consumption or usage of a specified product rather than on a flat rate for Reservation items. Note that defining Pay-As-You-Go item requires to enable the corresponding capability first. Reservation and Pay-As-You-Go items share same states and transitions on the Connect platform. Once a new item is created, the system assigns the *Draft* status to it. In case a new product version with this item is created, the system transfers the item to the *Published* state. Thereafter, Vendors can assign the *End of Sale* status to their item. Note, however, that system enables Vendors to restore the *Published* status to such items. -## Available Statuses -The list below displays available item states on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Draft](s-a-draft.html) -* B. [Published](s-b-published.html) -* C. [End of Sale](s-c-endsale.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Item Creation](t-1-new-draft.html) -2. [Item Publication](t-2-draft-published.html) -3. [Draft Removal](t-3-draft-deleted.html) -4. [End of Sale Assignment](t-4-published-endsale.html) -5. [Item Restoration](t-5-endsale-published.html) -## Learn more -Refer to the [Connect community page](https://staging.connect.cloudblue.com/community/modules/products/items/) for more details. +## Additional Information +Please refer to the [Products Management module](https://connect.cloudblue.com/community/modules/products/items/) documentation for more details. diff --git a/listings-request/object.md b/listings-request/object.md index 2bed4ce..4977ee5 100644 --- a/listings-request/object.md +++ b/listings-request/object.md @@ -4,23 +4,6 @@ A *listing request* object represents a formal request to list a product on a sp The system allows Vendors to generate listing requests of the following types: *create* (requests to list a new product), *update* (requests to update listing data), or delete (requests to delist a product from the marketplace). Consequently, all listing requests should be processed by Distributors/ Resellers. Once a new listing request object is generated, the system assigns the *Draft* status to this object. Once Vendors submit their request to Distributor or Reseller systems, the request object is automatically assigned to the *Reviewing* state. Distributors or Resellers can start processing the request and transfer it to the *Deploying* state. In case the request processing is successful, Distributors/Resellers assign the *Completed* status to this request. Alternatively, Distributors/Resellers can reject request in case of an error and transfer it to the *Cancelled* state. -## Listing request statuses -The following list displays available statuses for listing requests on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Draft](s-a-draft.html) -* B. [Reviewing](s-b-reviewing.html) -* C. [Deploying](s-c-deploying.html) -* D. [Completed](s-d-completed.html) -* E. [Cancelled](s-e-cancelled.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Draft Request Creation](t-1-new-draft.html) -2. [Draft Request Removal](t-2-draft-deleted.html) -3. [Draft to Reviewing Request Convertion](t-3-draft-reviewing.html) -4. [Reviewing Request Approval](t-4-reviewing-deploying.html) -5. [Deployment Completion](t-5-deploying-completed.html) -6. [Deployment Cancellation](t-6-deploying-cancelled.html) -7. [Reviewing Request Rejection](t-7-reviewing-cancelled) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/listings/) for more information. +## Additional Information +Please refer to the [Listings Management Module](https://connect.cloudblue.com/community/modules/listings/) documentation for more information. diff --git a/listings/object.md b/listings/object.md index 7b315b4..821773b 100644 --- a/listings/object.md +++ b/listings/object.md @@ -4,21 +4,6 @@ Once Vendors decide to list their product to their selected marketplace, the sys Listing objects are managed via *Listing Requests*. Namely, these requests are used to list the specified product to the required marketplace, update the listing information, or remove the product from this marketplace. Therefore, Vendors generate a listing request in case it is required to create, update or delete listings. Distributors or Resellers can approve or reject listing request and consequently manage listing objects on the Connect platform. -## Listing Statuses -The following list displays available statuses for listing on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Not Listed](s-a-notlisted.html) -* B. [Listed](s-b-listed.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Listing Creation](t-1-new-notlisted.html) -2. [Listing Approval](t-2-notlisted-listed.html) -3. [Listing Rejection](t-3-notlisted.html) -4. [Termination Request](t-4-termination-request.html) -5. [Termination Apporoval](t-5-listing-termination.html) -6. [Update Request](t-6-update-request.html) -7. [Update Approval](t-7-listing-update.html) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/listings/) for more information. +## Additional Information +Please refer to the [Listings Management moduke](https://connect.cloudblue.com/community/modules/listings/) documentation for more information. diff --git a/offers/object.md b/offers/object.md index 71727f3..0269a23 100644 --- a/offers/object.md +++ b/offers/object.md @@ -4,23 +4,5 @@ Offers represents logical grouping of one or multiple product plans. Plans are s Once Vendors generate a new offer instance, the system assigns the *Private* status to this offer. Vendors are required to define their offer and save its public version to transfer it to the *Ready* state. In case Vendors add their offer to their listing request, the system assigns *Listed* state to this offer. The following provides more information on available offer statuses and transitions on the CloudBlue Connect platform. -## Available Statuses -The list below displays available offer statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Private](s-a-private.html) -* B. [Ready](s-b-ready.html) -* C. [Listed](s-c-listed.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Offer Instance Creation](t-1-new-private.html) -2. [Public Version Creation](t-2-priv-ready.html) -3. [Adding an Offer to Product Listing](t-3-ready-listed.html) -4. [Offer Delisting](t-4-listed-ready.html) -5. [Private Offer Removal](t-5-priv-deleted.html) -6. ["Ready" Offer Instance Removal](t-6-ready-deleted.html) -7. [Ready to Private Version Assignment](t-7-ready-private.html) - -## Learn more -Refer to the [Connect community page](https://staging.connect.cloudblue.com/community/modules/offers/) for more information. +## Additional Information +Please refer to the [Offers Management Module](https://connect.cloudblue.com/community/modules/offers/) documentation for more information. diff --git a/partners/object.md b/partners/object.md index 29bba34..48d0119 100644 --- a/partners/object.md +++ b/partners/object.md @@ -5,19 +5,5 @@ In case an invitation link is generated, the system creates a new partner object Alternatively, you can instantly create and activate your partner account on the Connect platform. Note that the system also allows terminating contracts with your partners. In this case, your partner account will be *removed* from your partner list. -## Available Statuses -The following introduces available statuses for partner objects on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Invited](s-a-invited.html) -* B. [Active](s-b-active.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Partner Invitation](t-1-new-invited.html) -2. [Partner Account Creation](t-2-new-active.html) -3. [Invitation Link Activation](t-3-inv-active.html) -4. [Contract Termination](t-4-act-removed.html) - - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/partners/) for more information. +## Additional Information +Please refer to the [Partners Management Module](https://connect.cloudblue.com/community/modules/partners/) documentation for more information. diff --git a/price-lists/object.md b/price-lists/object.md index b6840dc..f329417 100644 --- a/price-lists/object.md +++ b/price-lists/object.md @@ -5,25 +5,5 @@ Vendors can generate price list drafts by using the Connect platform. Thereafter Furthermore, the system enables Vendors to schedule price list activation. Thus, created draft list can be activated on specified time. Vendors are also able to unschedule price lists and transfer them back to *Draft* state. Note that in case the activated price list is no longer relevant, Vendors can terminate these lists. -## Price List Statuses -The following list displays available price lists statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: - -* A. [Draft](s-a-draft.html) -* B. [Scheduled](s-b-scheduled.html) -* C. [Active](s-c-active.html) -* D. [Terminated](s-d-teminated.html) - - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Draft Creation](t-1-new-draft.html) -2. [Price List Schedule](t-2-draft-scheduled.html) -3. [Schedule Cancellation](t-3-schedule-draft.html) -4. [Scheduled Pricing Activation](t-4-schedule-active.html) -5. [Draft Activation](t-5-draft-active.html) -6. [Price List Termination](t-6-active-terminated.html) -7. [Draft Removal](t-7-draft-deleted.html) - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/pricing/) for more details. +## Additional Information +Please refer to the [Price Management Module](https://connect.cloudblue.com/community/modules/pricing/) documentation for more details. diff --git a/products/object.md b/products/object.md index 4dce378..06ef6e1 100644 --- a/products/object.md +++ b/products/object.md @@ -3,20 +3,6 @@ Products represent substances, software or services that are provisioned, fulfilled, or manufactured by Vendors. Thus, Vendors configure their products and define all required product data via the **Products** module on the Connect platform. Product data include items (SKUs), product overview, provided media, and so on. Furthermore, Vendors can provide different versions of a product and send requests to list or delist these product versions on specified marketplaces. Once Vendors assign a version to a *Draft* product, it transfers to the *Published* state. Vendors can also delete a product or assign it with the *End of sale* status. The following provide detailed information about each product status and product transition on the CloudBlue Connect platform. -## Product Statuses -The list below displays all product statuses on the Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Draft](s-a-draft.html) -* B. [Published](s-b-listed.html) -* C. [End of Sale](s-c-endsale.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Draft Creation](t-1-new-draft.html) -2. [Product Version Assignment](t-2-draft-pub.html) -3. [Draft Removal](t-3-draft-del.html) -4. [End of Sale Confirmation](t-5-pub-end.html) -5. [Product Restoration](t-6-end-pub.html) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/products/) for more information. +## Additional Information +Please refer to the [Products Management Module](https://connect.cloudblue.com/community/modules/products/) documentation for more information. diff --git a/program-contracts/object.md b/program-contracts/object.md index b3d0015..794b79b 100644 --- a/program-contracts/object.md +++ b/program-contracts/object.md @@ -3,22 +3,6 @@ Distributors and Vendors sign their program contracts to set business partnerships through the CloudBlue Connect platform. Before creating a program contract, a Distributor must ensure that an associated program agreement is created. Alternatively, Distributors can generate program agreement and program contracts while creating a Vendor-type Partner account. Once a new program contract is created by a Distributor, the system trasnfers this contract to the *Pending* state until it is signed and *activated* by a Vendor. Note Distributors can delete a pending program contract. Therefore, the system removes the deleted contract from the database. Distributors can also terminate active contracts. In contrast, Connect stores *terminated* contracts and enables users to view the contract data. -## Contract Statuses -The following list displays available program contract statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Pending](s-a-pending.html) -* B. [Active](s-b-active.html) -* C. [Rejected](s-c-rejected.html) -* D. [Terminated](s-d-terminated.html) - -## Transitions -Choose a transition from the diagram or click on any of the following contextual links to access transition information: - -1. [Contract Creation](t-1-new-pending.html) -2. [Contract Activation](t-2-pend-active.html) -3. [Contract Rejection](t-3-pend-rejected.html) -4. [Contract Removal](t-4-pend-deleted.html) -5. [Contract Termination](t-5-act-terminated.html) - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/partners/contracts/program-contracts/) for more information. +## Additional Information +Please refer to the [Partners Management Module](https://connect.cloudblue.com/community/modules/partners/contracts/program-contracts/) documentation for more information. diff --git a/report-repositories/object.md b/report-repositories/object.md index e246444..1264c60 100644 --- a/report-repositories/object.md +++ b/report-repositories/object.md @@ -5,23 +5,5 @@ Once Connect users add their Git repository with custom report templates, the sy In case the system successfully processes the added repository, its corresponding object is automatically transferred to the *Ready* state. Otherwise, the system fails to process your added repository and assigns the *Failed* status to the repository object. Connect users can edit or update their report repositories with the *Failed* and *Ready* statuses. Note that the system also allows deleting repositories in the *Failed* state. -## Available Statuses -The following list contains available statuses for the report repository objects on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Configuring](s-a-configuring.html) -* B. [Ready](s-b-ready.html) -* C. [Failed](s-c-failed.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [New Repository Object Creation](t-1-new-configuring.html) -2. [Successful Repository Configuration](t-2-conf-ready.html) -3. [Repository Processing Failure](t-3-conf-failed.html) -4. [Repository Details Edit](t-4-fail-configuring.html) -5. [Repository Removal](t-5-fail-deleted.html) -6. [Repository Update](t-6-ready-configuring.html) - - -## Learn more -Refer to the [Account module documentation](https://connect.cloudblue.com/community/modules/account/reports/) from the Connect Community page for more information. +## Additional Information +Please refer to the [Account Management Module](https://connect.cloudblue.com/community/modules/account/reports/) documentation for more information. diff --git a/report-schedules/object.md b/report-schedules/object.md index 10b662e..889961d 100644 --- a/report-schedules/object.md +++ b/report-schedules/object.md @@ -6,21 +6,5 @@ The system enables Connect users to edit provided trigger configuration as well Once a new report schedule object is genereted, the system assigns the *Enabled* status to it. Connect users can disable their schedules or switch them on again. Note that users can also delete disabled and enabled report schedule objects. -## Available Statuses -The following displays available report schedule statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Enabled](s-a-enabled.html) -* B. [Disabled](s-b-disabled.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [New Schedule Creation](t-1-new-enabled.html) -2. [Schedule Deactivation](t-2-enabled-disabled.html) -3. [Schedule Reactivation](t-3-disabled-enabled.html) -4. [Enabled Schedule Removal](t-4-enabled-deleted.html) -5. [Disabled Schedule Removal](t-5-disabled-deleted.html) - - -## Learn more -Refer to the [Report module documentation](https://connect.cloudblue.com/community/modules/reports/) from the Connect Community page for more information. +## Additional Information +Please refer to the [Reports Management Module](https://connect.cloudblue.com/community/modules/reports/) documentation for more information. diff --git a/reports/object.md b/reports/object.md index f84be78..4af75cd 100644 --- a/reports/object.md +++ b/reports/object.md @@ -2,20 +2,6 @@ ## Overview Reports represent instances that have data exported from the CloudBlue Connect platform. Reports can be especially useful to extract required data and import it to external systems for further processing, such as billing or reconciliation operations. Note that the system generates report files in the *XLSX* format. -## Report Statuses -The following list displays available report statuses on the Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Pending](s-a-pending.html) -* B. [Deploying](s-b-deploying.html) -* C. [Ready](s-c-ready.html) -* D. [Failed](s-d-failed.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Export Request Creation](t-1-new-pending.html) -2. [New Report Deployment](t-2-pen-deploying.html) -3. [Report Creation Success](t-3-dep-ready.html) -4. [Report Creation Failure](t-4-dep-failed.html) -5. [Report Removal](t-5-ready-remove.html) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/reports/) for more information. +## Additional Information +Please refer to the [Reports Management Module](https://connect.cloudblue.com/community/modules/reports/) documentation for more information. diff --git a/service-contracts/object.md b/service-contracts/object.md index 9e0a80e..4a7f0c8 100644 --- a/service-contracts/object.md +++ b/service-contracts/object.md @@ -2,22 +2,6 @@ ## Overview Service contracts are created by Distributors to invite Resellers into the CloudBlue Connect platform. Thus, signed service contracts enable Distributors to collaborate with Resellers and consequently create *syndication contracts*. Furthermore, by signing a service contract, Resellers can activate their Reseller Portal on the Connect platform. Alternatively, Distributors can generate service agreements and service contracts during the Reseller-type Partner account creation. Once a new service contract is created by a Distributor, the system transfers this contract to the *Pending* state until it is signed and *activated* by a Reseller. Note that Distributors can delete a pending service contract. Therefore, the system removes the deleted contract from the database. Distributors can also terminate active contracts. In contrast, Connect stores *terminated* contracts and enables users to view the contract data. -## Contract Statuses -The following list displays available service contract statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Pending](s-a-pending.html) -* B. [Active](s-b-active.html) -* C. [Rejected](s-c-rejected.html) -* D. [Terminated](s-d-terminated.html) - -## Transitions -Choose a transition from the diagram or click on any of the following contextual links to access transition information: - -1. [Contract Creation](t-1-new-pending.html) -2. [Contract Activation](t-2-pend-active.html) -3. [Contract Rejection](t-3-pend-rejected.html) -4. [Contract Removal](t-4-pend-deleted.html) -5. [Contract Termination](t-5-act-terminated.html) - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/partners/contracts/service-contracts/) for more information. +## Additional Information +Please refer to the [Partners Management Module](https://connect.cloudblue.com/community/modules/partners/contracts/service-contracts/) documentation for more information. diff --git a/subscriptions-fulfillment-request/object.md b/subscriptions-fulfillment-request/object.md index 084debe..e1dd3d2 100644 --- a/subscriptions-fulfillment-request/object.md +++ b/subscriptions-fulfillment-request/object.md @@ -3,36 +3,6 @@ Fulfillment requests (also referred to as subscription requests) are generated in case your customer purchased a product that is defined on the Connect platform and listed within a specified marketplace. The Connect platform features different request types. For example, purchase requests are generated in case a new order is created, a cancel request is generated if a customer decides to cancel the order, change requests are created in case the number of purchased items is changed, and so on. Fulfillment requests help Vendors, Distributors and Resellers to consolidate order fulfillment workflow and relevant state of the subscription objects on the platform. Therefore, Connect users can systematize product arrangements, subscription changes and order cancellations and streamline communication with partners simply by approving or rejecting fulfillment request. Note that each approved or rejected fulfillment requests correlate with a particular subscription state. Thus, for instance, approving purchase requests activates subscriptions, while rejecting these requests terminates them. Furthermore, the CloudBlue Connect platform populates fulfillment requests with various provisioning data that can be essential for many businesses and collaborations. -## Fulfillment request statuses -The following list showcases available statuses for fulfillment requests on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed information on your selected request status: -* A. [Draft](s-a-draft.html) -* B. [Pending](s-b-pending.html) -* C. [Tiers Setup](s-c-tiers-setup.html) -* D. [Inquiring](s-d-inquiring.html) -* E. [Approved](s-e-approved.html) -* F. [Failed](s-f-failed.html) -* G. [Scheduled](s-g-scheduled.html) -* H. [Revoking](s-h-revoking.html) -* I. [Revoked](s-i-revoked.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Pending Request Creation](t-1-new-pending.html) -2. [Draft Request Creation](t-2-new-draft.html) -3. [Draft to Pending Convertion](t-3-draft-pending.html) -4. [Draft Request Removal](t-4-draft-deleted.html) -5. [Pending to Tiers Setup Convertion](t-5-pending-tiers-setup.html) -6. [Tier Configuration Failure](t-6-tiers-setup-failed.html) -7. [Completed Tiers Configuration](t-7-tiers-setup-pending.html) -8. [System Parameters Inquiry](t-8-pending-inquiring.html) -9. [Vendor Parameters Inquiry](t-9-pending-inquiring.html) -10. [Inquiring Data Provision](t-10-inquiring-pending.html) -11. [Pending Request Approval](t-11-pending-approved.html) -12. [Pending Request Rejection](t-12-pending-failed.html) -13. [Schedule Delayed Activation](t-13-pending-scheduled.html) -14. [Scheduled to Pending Convertion](t-14-scheduled-pending.html) -15. [Request Revocation](t-15-scheduled-revoking.html) -16. [Revocation Confirmation](t-16-revoked-revoked.html) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/subscriptions/fulfillment-requests/) for more information on fulfillment requests. +## Additional Information +Please refer to the [Subscriptions Management Module](https://connect.cloudblue.com/community/modules/subscriptions/fulfillment-requests/) documentation for more information on fulfillment requests. diff --git a/subscriptions/object.md b/subscriptions/object.md index 477d112..0452b70 100644 --- a/subscriptions/object.md +++ b/subscriptions/object.md @@ -2,29 +2,6 @@ ## Overview A subscription on the Connect platform is an object that represents what your customers actually purchased (e.g., physical goods) or subscribed to (e.g., software as a service licenses). Moreover, subscriptions store product activation data and inquired information that can be specified during the Ordering phase or Fulfillment phase. Provided subscription data is interconnected with the provided product configuration and fulfillment requests on the Connect platform. Thus, for instance, a purchase fulfillment request creates a subscription, while a cancel request terminates it. Note that subscriptions can also be used for billing consolidation operations. Therefore, this provides business partners with a systematic way to consolidate billing data for each product arrangement. -## Susbcription Statuses -The following list displays available subscription statuses on the Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Processing](s-a-processing.html) -* B. [Active](s-b-active.html) -* C. [Terminating](s-c-terminating.html) -* D. [Terminated](s-d-teminated.html) -* E. [Suspended](s-e-suspended.html) -* F. [Draft](s-f-draft.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Subscription Creation](t-1-new-subscription.html) -2. [Subscription Approval](t-2-pro-active.html) -3. [Subscription Rejection](t-3-pro-terminated.html) -4. [Subscription Cancellation](t-4-active-terminating.html) -5. [Cancellation Approval](t-5-terminating-terminated.html) -6. [Change Request Creation](t-6-change-request.html) -7. [Change Request Approval](t-7-change-approval.html) -8. [Subscription Suspension](t-8-suspend.html) -9. [Subscription Resumption](t-9-resume.html) -10. [Draft Creation](t-10-draft.html) -11. [Draft Removal](t-11-draft-removal.html) -12. [Draft to Processing Convertion](t-12-draft-processing.html) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/subscriptions) for more information. +## Additional Information +Please refer to the [Subscriptions Management Module](https://connect.cloudblue.com/community/subscriptions) documentation for more information. diff --git a/syndication-contracts/object.md b/syndication-contracts/object.md index cd3664f..148bfdc 100644 --- a/syndication-contracts/object.md +++ b/syndication-contracts/object.md @@ -2,21 +2,6 @@ ## Overview Resellers enroll their Syndication Contracts to collaborate with Distributors on the CloudBlue Connect platform. The system requires Distributors to create a Syndication Agreement that serves as the template for these contracts. Otherwise, Resellers cannot enroll syndication contracts. Once Resellers enroll a new syndication contract, the system transfers this contract to the *Pending* state until it is signed and *activated* by their Distributors. Note that Distributors can also terminate active contracts after its activation. Connect stores *terminated* contracts and allows reviewing the deleted contract data. -## Contract Statuses -The following list displays available syndication contract statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: -* A. [Pending](s-a-pending.html) -* B. [Active](s-b-active.html) -* C. [Rejected](s-c-rejected.html) -* D. [Terminated](s-d-terminated.html) - -## Transitions -Choose a transition from the diagram or click on any of the following contextual links to access transition information: - -1. [Contract Creation](t-1-new-pending.html) -2. [Contract Activation](t-2-pend-active.html) -3. [Contract Rejection](t-3-pend-rejected.html) -4. [Contract Termination](t-5-act-terminated.html) - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/partners/contracts/syndication-contracts/) for more information. +## Additional Information +Please refer to the [Partners Management Module](https://connect.cloudblue.com/community/modules/partners/contracts/syndication-contracts/) documentation for more information. diff --git a/tier-account-requests/object.md b/tier-account-requests/object.md index 9e457b7..bd83cad 100644 --- a/tier-account-requests/object.md +++ b/tier-account-requests/object.md @@ -3,21 +3,5 @@ Tier Account Requests represent objects that store changes to the customer and reseller account object attributes. A tier account request is generated in case tier account information is edited. These request enable Distributors to consolidate tier account data with Vendors. Therefore, Partners can keep track of all tier account changes and updates. In case the **Tier Accounts Sync** capability is disabled, your generated tier account request is automatically transferred to the *Unsupported* state. Once this capability is switched on, a new created pending request is assigned to the *Pending* status until it is accepted or ignored by Vendor. -## Request Statuses -The following list displays available tier account request statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: - -* A. [Pending](s-a-pending.html) -* B. [Unsupported](s-b-unsupported.html) -* C. [Accepted](s-c-accepted.html) -* D. [Ignored](s-d-ignored.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Pending Request Creation](t-1-new-pending.html) -2. [Unsupported Request Creation](t-2-new-unsupported.html) -3. [Request Acceptance](t-3-pen-accepted.html) -4. [Request Ignore](t-4-pen-ignored.html) - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/customers/) for more information. +## Additional Information +Please refer to the [Customers Management Module](https://connect.cloudblue.com/community/modules/customers/) documentation for more information. diff --git a/tier-accounts/object.md b/tier-accounts/object.md index 59f7f9c..f222efc 100644 --- a/tier-accounts/object.md +++ b/tier-accounts/object.md @@ -4,16 +4,5 @@ Tier accounts represent objects that store customer or reseller account attribut Once a new tier account object is generated, the system assigns the *Active* status to this object. Therefore, the system allows utilizing customer and reseller data to generate subscriptions, create fulfillment request, and more. Note that Connect also enables to change customer or reseller data. Tier account object, however, remain in *Active* state. In case your tier accounts are removed, the system transfers such objects to the *Decommissioned* state. Therefore, such objects cannot be used to generate subscriptions or fulfillment request. -## Available Statuses -The following list displays available statuses of the tier account objects on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Active](s-a-active.html) -* B. [Decommissioned](s-b-decom.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Tier Account Creation](t-1-new-active.html) -2. [Tier Account Removal](t-2-act-decom.html) - -## Learn more -Refer to the [Customers module documentation](https://connect.cloudblue.com/community/modules/customers/) from the Connect Community page for more details. +## Additional Information +Please refer to the [Customers Management Module](https://connect.cloudblue.com/community/modules/customers/) documentation from the Connect Community page for more details. diff --git a/tier-config-request/object.md b/tier-config-request/object.md index 1b69e45..92109d4 100644 --- a/tier-config-request/object.md +++ b/tier-config-request/object.md @@ -5,33 +5,5 @@ The system generates a tier configuration instance and a tier request in case a The system assigns the *Pending* status to new tier requests. Vendors can approve or reject requests and transfer tier requests to corresponding states. In case a tier request validation capability is enabled, the system assigns new request to the Draft state. Note that in case parameter value should be specified, such tier requests are assigned to the *Inquiring* state. Furthermore, note that the system can generate T1-level and T2-level requests and corresponding tier configurations depending on specified product parameters. In case your product includes both Tier 1 and Tier 2 parameters, the system transfers Tier 1-level request to the *Tier Setup* state. -## Tier request statuses -The list below displays available statuses for tier configuration requests on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: - -* A. [Draft](s-a-draft.html) -* B. [Pending](s-b-pending.html) -* C. [Tiers Setup](s-c-tiers-setup.html) -* D. [Inquiring](s-d-inquiring.html) -* E. [Approved](s-e-approved.html) -* F. [Failed](s-f-failed.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [New Draft Creation](t-1-new-draft.html) -2. [Pending Request Creation](t-2-new-pending.html) -3. [Draft Removal](t-3-draft-deleted.html) -4. [Draft Validation](t-4-draft-pending.html) -5. [Inquiring Data](t-5-pend-inquiring.html) -6. [Parameter Value Assignment](t-6-inq-pending.html) -7. [Tier Setup to Inquiring Transition](t-7-tier-inquiring.html) -8. [Completing Tier Setup](t-8-tier-pending.html) -9. [New Inquiring Request](t-9-new-inquiring.html) -10. [New Tier Setup Request](t-10-new-tiers.html) -11. [Draft to Inquiring Transition](t-11-draft-inquiring.html) -12. [Draft to Tier Setup Transition](t-12-draft-tiers.html) -13. [Inquiring Request Rejection](t-13-inq-failed.html) -14. [Tier Request Approval](t-14-pend-approved.html) -15. [Pending Request Rejection](t-15-pend-failed.html) -16. [Tier Setup Request Rejection](t-16-tier-failed.html) -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community//tier-config/) for more information. +## Additional Information +Please refer to the [Tier Config Management Module](https://connect.cloudblue.com/community//tier-config/) documentation for more information. diff --git a/tier-config/object.md b/tier-config/object.md index 653baa2..ec19072 100644 --- a/tier-config/object.md +++ b/tier-config/object.md @@ -3,22 +3,6 @@ Tier Configuration (Tier Config) instances are used to assign configuration parameters to certain reseller accounts within the Distributor’s tiers hierarchy. These instances help partners manage and consolidate reseller information on the CloudBlue Connect platform. The system generates a tier configuration object and its associated tier request in case a specified product includes any **Tier Scope** parameter and a fulfillment request with this product is created. Once a new tier config instance is created, the system assigns the *Processing* state to this tier config. Thereafter, Vendors are required to process a generated tier request and consequently transfer this tier config instance to the *Active* state. Note that the Connect platform also allows implementing dynamic validation of draft tier request in case the corresponding product capability is enabled. Therefore, the system transfers new tier config instances to the *Draft* state. If draft configs are successfully validated, the system assigns the *Processing* status to them. Otherwise, draft configs are removed. -## Available Statuses -The list below displays available tier config statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: -* A. [Draft](s-a-draft.html) -* B. [Processing](s-b-processing.html) -* C. [Active](s-c-active.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [New Processing Config](t-1-new-processing.html) -2. [Draft Config Creation](t-2-new-draft.html) -3. [Draft Config Validation](t-3-draft-processing.html) -4. [Draft Config Removal](t-4-draft-deleted.html) -5. [Config Activation](t-5-pro-active.html) -6. [Config Update](t-6-act-processing.html) - - -## Learn more -Refer to the [Connect community page](https://staging.connect.cloudblue.com/community/modules/tier-config/) for more information. +## Additional Information +Please refer to the [Tier Config Management module](https://connect.cloudblue.com/community/modules/tier-config/) documentation for more information. diff --git a/usage-files/object.md b/usage-files/object.md index 46e8946..dda3e07 100644 --- a/usage-files/object.md +++ b/usage-files/object.md @@ -5,34 +5,5 @@ Note that Vendors are required to create a usage file object on Connect before u Once Vendors submit the usage file object to their business partners, the system allows Distributors or Resellers to accept or reject the usage file and assign the corresponding state to the object. In case the usage file is approved, Distributors and Resellers can launch all required billing operations. Once all billing operations are accomplished, the system allows Distributors or Resellers to close usage file and transfer the object to the corresponding state. -## Report Statuses -The following list displays available usage file statuses on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: - -* A. [Draft](s-a-draft.html) -* B. [Uploading](s-b-uploading.html) -* C. [Processing](s-c-processing.html) -* D. [Invalid](s-d-invalid.html) -* E. [Ready](s-e-ready.html) -* F. [Pending](s-f-pending.html) -* G. [Rejected](s-g-rejected.html) -* H. [Accepted](s-h-accepted.html) -* I. [Closed](s-i-closed.html) - -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [Usage File Creation](t-1-new-draft.html) -2. [Usage File Uploading](t-2-draft-uploading.html) -3. [Usage File Processing](t-3-upl-processing.html) -4. [Processing Failure](t-4-pro-invalid.html) -5. [Invalid File Reuploading](t-5-inv-uploading.html) -6. [File is Processed](t-6-pro-ready.html) -7. [Processed File Reuploading](t-7-ready-uploading.html) -8. [File is Submitted](t-8-ready-pending.html) -9. [Pending File Rejection](t-9-pend-rejected.html) -10. [Rejected File Reuploading](t-10-reject-uploading.html) -11. [Usage File Acceptance](t-11-pend-accepted.html) -12. [Usage File Closure](t-12-accept-closed.html) - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/usage/) for more information. +## Additional Information +Please refer to the [Usage Management Module](https://connect.cloudblue.com/community/modules/usage/) documentation for more information. diff --git a/usage-records/object.md b/usage-records/object.md index 1500b02..6ae647e 100644 --- a/usage-records/object.md +++ b/usage-records/object.md @@ -4,28 +4,5 @@ Usage records is your specified data that is associated with your required subsc Your usage record workflow is interconnected with the workflow of your provided usage file. Namely, once Vendor upload their spreadsheet file, the system assigns the *Uploaded* status to all provided usage record. In case your usage record includes data in wrong format or any other error, the system assigns the *Invalid* status to this record and usage file. Otherwise, the system transfers the usage record object to the *Validated* state. Once Vendors submit their usage file to Distributors or Resellers, the system assigns the *Pending* status to the usage file object and each provided usage record object. Distributors or Resellers can accept or reject usage file and consequently assigns corresponding statuses to all usage records. In case usage record is rejected, Vendors can fix the identified issues and reupload usage file with required records once again. In case usage records are accepted, Distributors or Resellers can use this record for their subsequent billing operations. Once all billing operations are accomplished, the system allows Distributors or Resellers close the provided usage file and its usage records. -## Report Statuses -The following list displays available statuses of usage record objects on the CloudBlue Connect platform. Select a status from the provided diagram or click on a contextual link below to display detailed status information: - -* A. [Uploaded](s-a-uploaded.html) -* B. [Validated](s-b-validated.html) -* C. [Invalid](s-c-invalid.html) -* D. [Pending](s-d-pending.html) -* E. [Rejected](s-e-rejected.html) -* F. [Accepted](s-f-accepted.html) -* G. [Closed](s-g-closed.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [New Record Creation](t-1-new-uploaded.html) -2. [Record Validation](t-2-upl-validated.html) -3. [Failed Record Processing](t-3-upl-invalid.html) -4. [Record Reuploading](t-4-inv-uploaded.html) -5. [Record is Submitted](t-5-val-pending.html) -6. [Record is Rejected](t-6-pend-rejected.html) -7. [Rejected Record Reuploading](t-7-rej-uploaded.html) -8. [Record Acceptance](t-8-pend-accepted.html) -9. [Record Closure](t-9-acc-closed.html) - -## Learn more -Refer to the [Connect community page](https://connect.cloudblue.com/community/modules/usage-module/) for more information. +## Additional Information +Please refer to the [Usage Management Module](https://connect.cloudblue.com/community/modules/usage-module/) documentation for more information. diff --git a/users/object.md b/users/object.md index b3daf69..f5e645e 100644 --- a/users/object.md +++ b/users/object.md @@ -2,20 +2,6 @@ ## Description Users represent employees and team members at your organization, such as IT specialists, managers, and sales representatives, who can access the CloudBlue Connect platform. Once a new user is added to the Connect platform, the system generates a user object and assigns the *Invited* status to this object. In case your invited user successfully activates the provided invitation, the system transfers this object to the *Joined* state. Otherwise, the invitation can be revoked and thus the user object can be assigned to the *Expired* status. Note, however, that the system allows resending invitations and transferring expired user objects back to the *Invited* state. -## Available Statuses -The list below displays available statuses of the user objects on the CloudBlue Connect platform. Select a status from the provided diagram or click on any of the following contextual links to access detailed status information: -* A. [Invited](s-a-invited.html) -* B. [Joined](s-b-joined.html) -* C. [Expired](s-c-expired.html) -## Transitions -Choose a transition from the provided diagram or click on any of the following contextual links to access transition information: - -1. [User Invitation](t-1-new-invited.html) -2. [Invitation Activation](t-2-inv-joined.html) -3. [Invitation Revocation](t-3-inv-expired.html) -4. [Invitation Resent](t-4-exp-invited.html) -5. [User Removal](t-5-joined-deleted.html) - -## Learn more -Refer to the [Account module documentation](https://connect.cloudblue.com/community/modules/account/users/) from the Connect Community page for more details. +## Additional Information +Please refer to the [Account Management Module](https://connect.cloudblue.com/community/modules/account/users/) documentation for more details.