Stages Documentation

<cms-type name="sharepointonlinegraph">
    <!-- Global Properties -->
    <cms-host ident="sharepoint.online.ident" name="https://your-company.sharepoint.com" displayName="SharePoint Online Example">
        <!-- Host Properties -->
        <cms-property name="client.id" value="xxxx-xxxx-xxxx-xxxx-xxxx" />
        <cms-property name="client.secret" value="xxxxxx" />
        <cms-property name="tenant.id" value="xxxx-xxxx-xxxx-xxxx-xxxx" />
        <cms-property name="state.attribute.name" value="_Status" />
    </cms-host>
</cms-type>

These configuration properties affect the behavior of one SharePoint Online server.

client.id

• Default Value: N/A
• Description: The client id of the stages application, which has to be registered at Microsoft Azure Portal.

client.secret

• Default Value: N/A
• Description: The client secret, which can be generated after registering the stages application at Microsoft Azure Portal.

tenant.id

• Default Value: N/A
• Description: The tenant id identifies your company when using Microsoft Services. You can get this id at Microsoft Azure Portal.

state.attribute.name

• Default Value: N/A
• Description: This property specifies a column name, which will be used by stages to store the file status.

use.system.account.for.download

• Default Value: false
• Description: When set to true, files will be downloaded from stages using the system account.

[stages-server-url]/stages/app/files/oauth_callback

- Commit comments for file versions
For each checkin of a file, the user can attach a comment for the version which gets created.
The Microsoft Endpoint, which is used to read that information, delivers the same checkin comment for each version. This comment is simply the latest checkin comment. (Opened issue at Github)

- Behavior of Lock/Unlock
Currently, the graph API only supports checkin/checkout and no Undo-Checkout. So for every lock/unlock a new version of that file is created in sharepoint online.

- Initial commit
Creates two versions (one for the creation of a new file/ second for updating the properties)