Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
74:cms_sharepoint_online [2020/05/20 07:05] – tssr74:cms_sharepoint_online [2021/03/03 14:57] – fnpk
Line 17: Line 17:
     </cms-host>     </cms-host>
 </cms-type> </cms-type>
 +
  
 </code> </code>
Line 30: Line 31:
 Properties marked with ** # ** are required but can also be set in the //File Management// section in the Stages web-application as well. The value entered in the web-application overrides the one from the config.xml. Properties marked with ** # ** are required but can also be set in the //File Management// section in the Stages web-application as well. The value entered in the web-application overrides the one from the config.xml.
  
-**+ ** ''Required but with default'' \\ +''Required but with default'' \\ 
-Properties marked with ** + ** are required, but there is a default value. This values can be overridden by configuring it in the config.xml.+Properties marked with are required, but there is a default value. This values can be overridden by configuring it in the config.xml.
  
 > client.id ** * ** > client.id ** * **
Line 48: Line 49:
   * Links: [[https://portal.azure.com|Microsoft Azure Portal]]   * Links: [[https://portal.azure.com|Microsoft Azure Portal]]
  
-> loginserver ** + **+> loginserver
  
   * Default Value: <nowiki>https://login.microsoftonline.com/</nowiki>   * Default Value: <nowiki>https://login.microsoftonline.com/</nowiki>
Line 54: Line 55:
   * Links: [[https://oauth.net/|More about OAuth]]   * Links: [[https://oauth.net/|More about OAuth]]
  
-> scope ** + **+> scope
  
   * Default Value: offline_access User.Read Sites.ReadWrite.All   * Default Value: offline_access User.Read Sites.ReadWrite.All
Line 63: Line 64:
   * Description: This property specifies a column name, which will be used by stages to store the file status.   * Description: This property specifies a column name, which will be used by stages to store the file status.
  
-> document.content.type.name ** + **+> document.content.type.name
  
   * Default Value: Document   * Default Value: Document
   * Description: Name of the **document**  content type. Sharepoint supports multiple content types but stages only supports the default type for documents.   * Description: Name of the **document**  content type. Sharepoint supports multiple content types but stages only supports the default type for documents.
  
-> link.content.type.name ** + **+> link.content.type.name
  
   * Default Value: Link to a document   * Default Value: Link to a document
Line 75: Line 76:
   * Known Issue: Typo in Default Value. Has to be Link to a **D**ocument   * Known Issue: Typo in Default Value. Has to be Link to a **D**ocument
  
-> use.system.account.for.download ** + **+> use.system.account.for.download
  
   * Default Value: false   * Default Value: false
Line 105: Line 106:
  
 === Repository Configuration === === Repository Configuration ===
-Access to SharePoint Online projects can be configured in Stages processes via “Management > File Management > Repositories”. 
-{{ :cms:spo-repository.png? |}} 
  
-> Name: +Access to SharePoint Online projects can be configured in Stages processes via “Management > File Management > Repositories”. [[https://doc.stagesasaservice.com/lib/exe/detail.php?id=74:cms_sharepoint_online&media=cms:spo-repository.png|{{  :cms:spo-repository.png  }}]]
-The name of this SharePoint Online configuration. This name will be used by Stages to refer to this repository configuration (e.g. in repository plan)+
  
-> Host: +> Name:  The name of this SharePoint Online configuration. This name will be used by Stages to refer to this repository configuration (e.g. in repository plan)
-This selection field contains an entry for each cms-host section in the Stages configuration file (config.xml). You can select the host for this repository configuration.+
  
-> Site: +> Host:  This selection field contains an entry for each cms-host section in the Stages configuration file (config.xml). You can select the host for this repository configuration.
-Define a site parameter for this repository configuration. The site is the path to the location, where your document libraries are located on the SharePoint server. The site is one piece for the complete connection string to the SharePoint server. The connection string is build like that: // | host.url | : | port | | **/site/** | | documentLibrary | //.+
  
-This overwrites the **path** from the URL entered in the configuration file (config.xml).+> Site:  Define a site parameter for this repository configuration. The site is the path to the location, where your document libraries are located on the SharePoint server. The site is one piece for the complete connection string to the SharePoint server. The connection string is build like that: // | host.url | : | port | | **/site/**  | | documentLibrary | //. 
 + 
 +This overwrites the **path**  from the URL entered in the configuration file (config.xml).
  
 Example: Example:
Line 126: Line 124:
   * The path from the config.xml gets overwritten by the value from Repository Path.   * The path from the config.xml gets overwritten by the value from Repository Path.
  
-> Document Library: +> Document Library:  Defines the name of the document library. The document library is one piece for the complete connection string to the SharePoint server. The connection string is build like that: // | host.url | : | port | | /site/ | | **documentLibrary**  | //.
-Defines the name of the document library. The document library is one piece for the complete connection string to the SharePoint server. The connection string is build like that: // | host.url | : | port | | /site/ | | **documentLibrary** | //. +
- +
-> Root Folder: +
-Defines a root folder **inside** the given document library. Every file linked or uploaded to a repository, which defines a root folder in the configuration, will be **inside** this root folder. +
- +
-> Default Lifecycle +
-Select a lifecycle from the process metamodel as default for files from this repository. +
- +
- +
-==== Known Limitations ==== +
- +
-== 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) +
- +
-== Set State == +
- +
-After setting the state of a Sharepoint Online document, the assignment to the Stages user gets lost. The modifier will be the Sharepoint Online user instead of the Stages user.+
  
-== Major / Minor Version ==+> Root Folder:  Defines a root folder **inside**  the given document library. Every file linked or uploaded to a repository, which defines a root folder in the configuration, will be **inside**  this root folder.
  
-The Graph API, wich is used by the SharePoint Online Adapter, does currently not support setting major/minor versions when uploading a file.+> Default Lifecycle  Select a lifecycle from the process metamodel as default for files from this repository.