Installing Shareflex on your SharePoint tenant

Installing Shareflex on your SharePoint Online Tenant

Updated 23 May 2024 by Marten Vosmer

This post will guide you through all the steps and understandings that are necessary to install Shareflex on your SharePoint tenant.

Introducing third-party cloud based SaaS solutions for Microsoft SharePoint Online

It’s possible to run third-party cloud solutions on SharePoint Online, which is obviously also a cloud-based platform by Microsoft. Despite both being cloud-based, third-party solutions can add additional solutions on top of SharePoint Online to meet specific business needs. This integration allows organizations to leverage the security, flexibility and scalability of SharePoint Online while enhancing it with specialized ready made solutions offered by these third-party providers.

One of the key aspects of (third-party) SaaS software, including SharePoint Online, is the subscription-based payment model. Customers pay for the software on a yearly basis, providing them with continuous access to the solution and its features. However, if a customer decides not to renew their subscription, the SaaS provider has the ability to deactivate the service.

Third-party solution providers utilize a processing model where certain actions performed by customers, such as saving a document, must be authorized by the third party solution provider. If the customer’s subscription is active and payment is up-to-date, the save operation is authorized, allowing the document to be saved successfully. However, if the customer’s subscription is no longer active due to non-payment or expiration, the save authorization is denied by the third party. As a result, the customer will encounter an error when attempting to save the document, preventing unauthorized usage of the solution.

For this approach to function effectively, an authorized connection between the customer’s environment and the third-party supplier are essential. These permissions are typically established and managed within the customer’s environment, allowing the third-party solution provider to interact with the customer’s SharePoint Online instance. These permissions are installed and configured by the customer and can be removed or modified by the customer at any time, giving them full control over the access rights granted to the third-party supplier. If the permissions are removed by the customer, the authorized connection between the customer’s environment and the third-party solution provider is severed. Consequently, the software provided by the third party will no longer function properly.

This modern SaaS approach stands in contrast to traditional on-premises software deployments, where customers typically pay a much higher upfront cost for perpetual licenses. With on-premises software, customers own the software outright and are not subject to potential service deactivation by the supplier. This ownership provides a sense of control and autonomy, as the supplier cannot dictate when the customer should stop using the software. One advantage of on-premises software is the assurance that the supplier does not have direct access to the customer’s environment. With data sovereignty and privacy becoming increasingly important considerations, some organizations may prefer the added control that comes with hosting software on their own servers.

While on-premises software offers complete control, SaaS solutions boast significantly lower yearly costs, eliminate the need for internal servers, and require fewer IT personnel. This streamlined approach ensures cost-effectiveness, scalability, and operational efficiency. However, the only disadvantage is that the third party supplier needs access to the customers SharePoint Online site to manage usage, which can be a consideration for some businesses.

Introducing Portal Systems AG Germany Shareflex

The solutions (Document Control, Contract Management and Document Management) offered on this website run on the Shareflex Online business application platform for SharePoint Online, which is created and owned by Portal Systems AG. Portal Systems AG is also the owner of these three business applications. MetaMail 365 is a solution built by Lialis on the Shareflex platform, thus, this solution is owned by Lialis. Portal Systems AG sells exclusively in German-speaking countries. Lialis, as an integration partner of Portal Systems, has the right to resell these solutions and the Shareflex platform, primarily to customers located outside the German-speaking regions. Occasionally, Lialis also offers its services to German-speaking companies.

Lialis provides all services needed to its customers for the deployment, support, training, and documentation of the Shareflex applications by competent and experienced employees. We can modify the applications to fit the needs of our customers, and we can also translate the applications into other languages.

Shareflex Online platform description

The Shareflex Online Solutions are ready-made or custom business applications for digital mapping, automation and optimization of business processes. The Shareflex Online Solutions are based on Microsoft 365 and the Shareflex Online Services. The Shareflex Online Solutions offer all important functions required for company-wide document and file management. Furthermore, individualizations can be made in order to meet the specific requirements and the continuous changes in the business environment.
The foundation of the Shareflex Online Solutions is Microsoft 365, which is extended by the Shareflex Online Services.

The Shareflex Solutions thus consist of a SaaS component (Shareflex Online Services) and scripts/resources that are provided to the customer as a copy for the duration of the contract and must be imported into the customer’s Microsoft 365 environment (Shareflex Online Solutions).

The following is a brief summary of the Shareflex Online Services:

  • Shareflex Forms provides user-friendly forms for displaying the SharePoint data of a Shareflex Solution.
  • Shareflex Rules provides backend business logic, e.g. when a contract is created, all the necessary data structures are automatically created in the background.
  • Shareflex Provisioning can be used to create and update the SharePoint information architecture (e.g. websites, lists/libraries, columns, content types).

These Shareflex Services are provided by a SharePoint App (Forms) and an Azure Enterprise Application (Rules and Provisioning).

The customer’s SharePoint tenant sends certain data (defined and restricted by business logic) to the Shareflex Online Services, where it is processed so that corresponding actions can be carried out on the customer’s SharePoint tenant. Changes to the customer’s documents and other (content) data are made exclusively in his Microsoft 365 environment.

Portal Systems manages the infrastructure (Infrastructure as a Service) hosted in Microsoft Azure data centres, including but not limited to configuration data management, high availability, configuration data recovery, security and scaling.

Portal Systems guarantees that all created and filed data and documents are stored exclusively in the customer’s own Microsoft 365 tenant.

Details on customer data processing activities performed by Portal Systems SaaS services

Portal Systems has chosen to create their own workflow application functionality / design. The SharePoint Online workflows and Power Automate workflows are not used. The reason for this choice is that creating their own workflow user interface and mechanism allows them to deliver an exceptional workflow experience to the end users. Power Automate workflows are considered too slow and do not support complex business processes, for example. Anyway, it is the choice of Portal Systems to go in this direction, which is also a suggested way by Microsoft (please see article about Remote Event Receivers below).

To deliver secure and trustworthy workflow outcomes and procedure, it is crucial that the content being approved cannot be altered by the user who is approving it, nor may the content under approval be modified by other users. If users can modify the content involved in the approval workflow, the workflow output cannot be trusted and can be inconsistent. To achieve a trustworthy workflow outcome, a mechanism is needed to set permissions for the workflow tasks and the content under approval. Workflow tasks must be created in a specific list, and end users should not be allowed to create, edit, or delete these tasks by default. A document may go through several workflow phases, and in each phase, the permissions for both the workflow task and the content under approval must be set and managed carefully. This permission management cannot be done by the end user, as they do not have sufficient permissions. If they did, the workflow outcome could not be trusted.

The big question is what mechanism will take care of this permission management and the workflow process in the background?

At a high level, SharePoint Online consists of the following parts: lists (to store metadata), libraries (to store documents), version logs, permissions handling, and a browser-enabled user interface. SharePoint Online does not offer the possibility to run scripts for customers under full permissions, e.g. SharePoint Online will not do this permission management for the customers. SharePoint just provides an user interface to set permissions. Usually (as already mentioned) endusers are not able to understand this interface and can not estimate the effect of this configuration. So a lot of third party software vendors provide a solution for this scenario.

A most used method to carry out the above-described permission management is to use .Net programming on Windows servers (cloud-based Azure, for example) communicating to the REST API of SharePoint Online which will do all the work in SharePoint Online. And this custom developed software will run with full permissions, making it possible to set all the permissions for the workflow tasks and the content under workflow approval for example. Shareflex is one of these custom developed programs and provides not only a more user friendly interface to configure permissions to the users, but also a fully JavaScript wrapped access to SharePoint Online REST API. So no .NET coding is necessary to configure customizations on top of the Shareflex permission standard.

Bottom line, if customers wants to utilize the high-end Shareflex applications on SharePoint Online and benefit from the functions, it can only be done with a central M365 services handling many tasks like the workflow content permission tasks described above. For this to work, Portal Systems services will require full permissions to the SharePoint Online site of the customer where the Shareflex applications are installed. The alternative is to use SharePoint standard functions or much less functional applications from other suppliers, where a central M365 component will be needed as well.

During the setup of the Shareflex online platform on the customer’s SharePoint Online tenant, these permissions must be granted as a so-called enterprise application.
All Shareflex applications for all customers make use of Portal Systems-managed M365 services, which are responsible for many tasks like those described above. The processing carried out by Portal Systems in the Azure-based Shareflex Online Service depends on the solution used and the type of customization. As a general rule, the following data will be exchanged between the customer and Portal Systems: metadata, workflow tasks, permissions, emails sent, groups and users assigned to groups, and deployment of the Shareflex applications, which consist of many parts.

All this customer data is passed from the customer to the Portal Systems services and then passed on to the SharePoint Online REST service of the customers tenant, which carries out the work in SharePoint Online.

Documents (Word files) do not pass-through Portal Systems, and Portal Systems does not store any customer content. If data is provided to the Portal Systems services it is just for data processing within the Portal Systems services. As mentioned this is a typical scenario also suggested by Microsoft to extend SharePoint Online functionality and to access SharePoint Online REST API.

Customers can remove the permissions granted to Portal Systems at any time. As a result, all save operations will fail, though the content will remain on the customer’s SharePoint environment and will be accessible for exports/downloads. If the customer does not renew the Shareflex subscription, Portal Systems will disallow all save operations, resulting in the same scenario.

Customer-based data processing is performed by Remote Event Receivers, which act as a connection between the customer and Portal Systems tenant.  All of this is done via MS Graph permissions that Portal Systems services have on the customer’s SharePoint Online environment. The permissions granted to Portal Systems services are limited to a specific SharePoint Online site collections where the Shareflex application is installed in. It’s important to note that these permissions granted by the customer do not allow access for individuals to browse the customer’s environment.

There are many remote event receivers (dozens to hundreds) executing numerous scripts. It’s impractical to track everything happening. The client could theoretically investigate it.

Remote event receivers are only executed when an item is created, updated, or deleted. Executing these rules requires metadata. Because rules are linked to event receivers, a lot of metadata is exchanged.

Practical Example 1:
New Sales Record: A user clicks the button to create a new sales record.
Form Appears: Fields are filled out, with no communication to Portal Systems yet.
Item Saved: Saving the item triggers an remote event receiver (only during save, update, or delete).
Event Trigger: The remote event receiver signals the service at Portal Systems tenant to perform an action. The service executes a JavaScript linked to the remote event receiver, communicates with the SharePoint REST API, and uses the retrieved metadata. Users can’t do this due to lack of permissions.
Permissions and Workflow: The Portal Systems services can create a workflow task in a workflow list, assign permissions (e.g., who can approve), and update item fields (e.g., status) upon approval. This can’t be done under a user account.

Schematic Example 2:
In the two slides below, the Shareflex workflow creation process is outlined in a flowchart. All the steps taken by the users and the interactions with the Portal Systems Service and SharePoint Online REST API are listed, showing how these interact with the customer’s SharePoint Online site.

 

Reasons for Portal Systems Managing the central API Server:

  • Intellectual Knowledge: Protects their know-how.
  • Centralized Administration: Easier updates and control.
  • Consistency: Ensures everyone uses the same API version.
  • Ownership: It’s their software but all data used in the application will always be in control by the customer and is stored in the customers SharePoint Online.
Requirements
  • A properly configured Microsoft/SharePoint environment, including SharePoint licenses for your users.
  • Shareflex licenses for all users that are going to use Shareflex one way or another (your tenant name will have to be shared with Portal Systems).
  • The Shareflex licensing data and SharePoint solution package file, which will be provided by Portal Systems once your Shareflex licenses are active.
  • A Microsoft 365 account with the “Global Administrator” role (most actions can be performed with a lower role, as described in each individual step).
  • A name for the SharePoint site that will be used to host your  Shareflex app(s). Note that this site must not yet exist.
1. Creating a new site dedicated for Shareflex

Keep in mind that while it is technically possible to install multiple Shareflex apps (as sub sites) on the same SharePoint site, certain apps (such as Shareflex Contract) will still require their own dedicated site. Thus, depending on what apps you want to deploy, you may need to follow the steps in this post multiple times.

Needed role: “SharePoint Administrator”

Navigate to the Active sites page within the SharePoint admin center:

https: // <TENANT> -admin.sharepoint.com/_layouts/15/online/AdminHome.aspx#/siteManagement

Click on Create, and in the dialog that opens choose the “Browse more sites” option.

Installing Shareflex on your SharePoint tenant - new site collection

Make sure to select the “Team site” template, and choose “../sites/” as the Site address prefix. All other info (including the site name) is up to you. Click on Finish to create the site.

Installing Shareflex on your SharePoint tenant - new shareflex site

If all went well, the value in the Template column of the created site should be set to “Team site (no Microsoft 365 group)”.

 

2. Enabling the creation of subsites

Shareflex uses SharePoint subsites to store core and application-specific resources. If subsite creation has not been enabled in your SharePoint settings, you will need to do so.

Needed role: “SharePoint Administrator”

Go to the Settings page of the SharePoint admin center, then open the “classic settings page”.

Installing Shareflex on your SharePoint tenant - site settings

Locate the “Subsite Creation” section, select the “Enable subsite creation for all sites” option, then scroll down and click on OK to save the setting.

3. Using the SharePoint Online Management Shell to update some properties

Needed role: “SharePoint Administrator”

Two properties will have to be updated through the SharePoint Online Management Shell:
– The DenyAddAndCustomizePages site property has to be disabled so that Shareflex can create custom properties, which is essential for it to properly function.
– The SiteOwnerManageLegacyServicePrincipalEnabled tenant property has to be enabled so that the permission scope of Shareflex’s SharePoint Add-in can be restricted to your created site.

On a Windows device, launch “Windows PowerShell ISE” as Administrator. Execute the following code to install the latest version of the SharePoint Online Management Shell:

“`

if (Get-Module -ListAvailable -Name Microsoft.Online.SharePoint.PowerShell) {
Update-Module -Name Microsoft.Online.SharePoint.PowerShell
}
else {
Install-Module -Name Microsoft.Online.SharePoint.PowerShell
}

“`

Installing Shareflex on your SharePoint tenant - new role shareflex admin

During the installation it may prompt you to install additional dependencies, or to trust the repository. If so, click on Yes. Once the installation finishes, it will briefly display a notification message:

 

Once the module is installed, connect to your SharePoint tenant by executing this command:

“`Connect-SPOService -Url https://<TENANT>-admin.sharepoint.com“`

In the Sign-in window that appears, log in using your SharePoint Administrator account.

Execute the following command to disable the DenyAddAndCustomizePages property of the site that you created earlier:

“`Set-SPOsite https://<TENANT>.sharepoint.com/sites/<CREATED-SITE> -DenyAddAndCustomizePages 0“`

Then execute this final command to enable the SiteOwnerManageLegacyServicePrincipalEnabled tenant property:

“`Set-SPOTenant -SiteOwnerManageLegacyServicePrincipalEnabled 1“`

Installing Shareflex on your SharePoint tenant - denyaddcustomizepages

4. Adding the Shareflex Online Services app to the Azure Active Directory (AAD)

This step should be skipped if you already have another Shareflex-enabled site on your SharePoint tenant.

Needed role: “Global Administrator”, “Application Administrator” or “Cloud Application Administrator”

Navigate to the URL that was communicated by Portal Systems. The URL should look like this:

https://login.microsoftonline.com/<TENANT>.onmicrosoft.com/v2.0/adminconsent?customer_id=<APP-ID>&response_type=token&scope=https%3A%2F%2F<TENANT>.sharepoint.com%2F.default&state=give-consent%20&redirect_uri=https%3A%2F%2Fwebsite-<APP-URL-PART>.azurewebsites.net

In the consent dialog that appears, accept the requested permissions.

Installing Shareflex on your SharePoint tenant - shareflex permissions required prompt

After accepting the permissions, you will be redirected to the Shareflex Online app. You can close this page.

5. Granting Shareflex Online Services access to SharePoint

Shareflex uses remote event receivers, which requires you to grant it access to SharePoint via a SharePoint App-Only authorization.

Needed role: “Global Administrator”, “Application Administrator” or “Cloud Application Administrator”

Head to the Enterprise applications page of the AAD, then locate and open the “Shareflex Online” app.

Granting Shareflex Online Services access to SharePoint

Go to the Properties section. Do not change anything, but write down the below three highlighted values:

Granting Shareflex Online Services access to SharePoint properties

Navigate to the App Permission page of the site that you created:

https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>/_layouts/15/appinv.aspx

Insert the AAD app values that you wrote down earlier into the fields on the page, as seen in the below screenshot.
Note that the “App Domain” field should not contain a “https://” prefix, unlike the “Redirect URL” field.

Installing Shareflex SharePoint Insert the AAD app values

Copy & paste this XML (without any changes) into the “App’s Permission Request XML” field:

<AppPermissionRequests AllowAppOnlyPolicy="true">
    <AppPermissionRequest Scope="http://sharepoint/content/sitecollection" Right="FullControl" />
</AppPermissionRequests>

Apply the permissions by clicking on Create, then click on “Trust It” to confirm.

installing shareflex sharepoint online trust app

 

Confirm that the permissions have been applied correctly by going to the Site App Permissions page from within the Site Settings of your created site.

installing shareflex sharepoint online site app settings

 

If everything is correct, you should be able to see an entry for the “Shareflex Online” app.

6. Setting the delegated app permissions

This step should be skipped if you already have another Shareflex-enabled site on your SharePoint tenant.

Needed role: “Global Administrator”, “Application Administrator” or “Cloud Application Administrator”

Navigate to the URL of the Shareflex Online app that will have been provided by Portal Systems. The URL will look like either

https://<website-APP-URL-PART>.azurewebsites.net

or

https://sfs<NUMBER>.portalsystems.de

installing shareflex sharepoint online deployment site

 

Enter the absolute URL of the site you that you created (e.g. https://contoso.sharepoint.com/sites/shareflex) into the “SharePoint site” field, then click on Enter.

In the dialog that appears, make sure to check the “Consent on behalf of your organization” checkbox, then click on Accept to agree to the requested permissions.

installing shareflex sharepoint online deployment site consent

Head back to the Enterprise applications page of the AAD, open the Shareflex Online app and click on the Permissions menu entry.
Verify that the listed permissions match the below screenshot.

installing shareflex sharepoint online graph permissions

7. Installing the Shareflex Core resources to your SharePoint site

Needed role: Site (Collection) Administrator

Now that all permissions have been properly configured, the Shareflex Online app can be used to install its required Core resources on your SharePoint site.

Navigate to either of the following URLs (depending on what domain was provided by Portal Systems) :

https://<website-APP-URL-PART>.azurewebsites.net/baf/?SPHostUrl=https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>

or

https://sfs<NUMBER>.portalsystems.de/baf/?SPHostUrl=https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>

 

Enter an email address into the “Administrative Contact” field and click on Save.

installing shareflex sharepoint online set admin contact name

Before moving on, make very sure that the display language of your Microsoft account matches the default language of your created site. This is a technical limitation that (only) applies during the execution of any Shareflex script (including the Core resources).

To check the default language of your created site, navigate to:

https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>/_layouts/15/muisetng.aspx

installing shareflex sharepoint online check default site language

To check the display language of your Microsoft account, navigate to:

https://myaccount.microsoft.com/settingsandprivacy/language

If they are different, (temporarily) change your account’s display language.

You can now start the installation of the Core resources by clicking on “Setup Core web now”, then on OK to confirm.

installing shareflex sharepoint online install core

 

The installation will take a couple of minutes. The page will auto-refresh until the installation completes.

installing shareflex sharepoint online install core progress

 

Once the installation has finished (the Job Log status should be green), click on the “Prepare as Master Site” button, then on OK to confirm.

installing shareflex sharepoint online prepare master site

 

After a few minutes the second Job Log should be green as well.

installing shareflex sharepoint online master site core results

 

Most of the Shareflex resources will have been deployed to the Shareflex Core subsite located at https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>/pscBAF. Feel free to look around.
You can also get to the Shareflex Core subsite by clicking on the “Core web” button on the Shareflex Online app page.

installing shareflex sharepoint online install shareflex resources

 

In the Settings menu of your SharePoint site (including its subsites such as Shareflex Core), you can now also find a menu entry to quickly navigate to the Shareflex Online app.

installing shareflex sharepoint online subsites content

Keep in mind that this link is site-specific, so whenever you use the Shareflex Online app (including the Provisioning customer), always double check if its context is set to the correct site:

installing shareflex sharepoint online provisioning site web client

8. Using the Shareflex Provisioning customer to deploy the Shareflex Addons on your SharePoint site
This step can only be performed if Portal Systems has granted you access to their Partner Portal.

Once you are logged in to the Partner Portal, click on the Deployments button.

installing shareflex sharepoint online shareflex provisioning deployments

Then open the “Shareflex Add-ons” folder and locate the latest version of the ShareflexAddons archive for SharePoint Online (O365).

installing shareflex sharepoint online add-ons deployment

Download the archive file and unzip it somewhere.

Needed role: Site (Collection) Administrator

In your own SharePoint tenant, head to the Deployment library inside of the Shareflex Core subsite:

https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>/pscBAF/Deployment

Then upload (e.g. by dragging and dropping) the entire “ShareflexAddons” folder to the Deployment library.

installing shareflex sharepoint online core addons deployment folder upload

Shareflex offers a complex proprietary XML-based scripting language that can be used to automate certain SharePoint & Shareflex actions.
Files making use of this language will have the “.beeml” file extension.

Inside the ShareflexAddons folder there should be a file called “ShareflexAddons.beeml”. Open this file with any text editor, and copy its contents.
Head back to the Shareflex Online app page (through the link in the Settings menu), select the Tools tab, and click on Open Web IDE.

installing shareflex sharepoint online msbaf setup

This Web IDE (also called Provisioning customer) allows you to execute *.beeml scripts.
Before executing anything, make sure that the “Start Web” field contains the URL to your created site (https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>).
The “User” and “Password” fields should be ignored.
The “File Name” field is useful for providing a short script description that can later be used to the execution jobs/logs. This is optional, but recommended.

Feel free to execute the default script as a test, by clicking on Execute. Then click on Autorefresh to view the execution progress in real-time.
If the script ran successfully, the progress log will end with “Script successfully executed”. Note that any warnings (unlike errors) are generally safe to ignore.

installing shareflex sharepoint online app provisioning client

Now delete the default script, and replace it with the contents from the “ShareflexAddons.beeml” file.
Before executing the script, perform a Precheck. This will quickly analyze the script to look for potential issues.

installing shareflex sharepoint online app provisioning client pre check

After the precheck finishes, click on Execute. The Shareflex Addons installation will take about two hours.

installing shareflex sharepoint online provisioning client execute

Note that the Provisioning customer runs all scripts as background jobs, so it is fine to close your browser.
At any point in time you can view the status/progress/history of a background job by clicking on the Joblist button within the Provisioning customer.

Which brings you to this background job overview:

Once the installation job finishes it will move to the Completed tab,  and its Run State will update to “Terminated (Normal)”, assuming that no problems arose.

9. Uploading the Shareflex Forms app to the SharePoint App Catalog

This step should be skipped if you already have another Shareflex-enabled site on your SharePoint tenant.

Needed role: “SharePoint Administrator”

Navigate to the App Catalog page within the SharePoint admin center:

https://<TENANT>-admin.sharepoint.com/_layouts/15/tenantAppCatalog.aspx

Upload the “shareflex-forms.sppkg” file that Portal Systems shared with you. This SharePoint solution package contains the customer-side web parts that are necessary to view Shareflex forms.

Once the upload finishes the “Enable app” dialog should automatically appear.
Select “Enable this app and add it to all sites, uncheck “Add to Teams” and then click on the Enable app button.

Once enabled it should look like this:

And that’s it!

Example: deploying the Shareflex Contract app
This step can only be performed if Portal Systems has granted you access to their Partner Portal.

Note that the Shareflex Contract app requires its own dedicated (Shareflex-enabled) site. If you don’t already have one, follow all of the above steps first.

Head to the Deployments library of the Partner Portal, open the Shareflex Contract folder, then locate the latest version of the ShareflexContract archive for SharePoint Online (O365).

Download the archive file and unzip it somewhere. It should contain two folders: “ShareflexContract” and “ShareflexAddons”. Open the latter and identify its version number by locating the subfolder that starts with an underscore.

 

Needed role: Site (Collection) Administrator

In your own SharePoint tenant, head to the Deployment library inside of the Shareflex Core subsite:

https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>/pscBAF/Deployment

If the library contains a ShareflexAddons folder, identify its version number in the same manner.

If the version number of the ShareflexAddons inside the Deployment folder is lower than the one included in the ShareflexContract archive, delete the entire ShareflexAddons folder from the Deployment library.

If the Deployment library does not contain a ShareflexAddons folder (anymore), upload the ShareflexAddons version included in the archive.

Finally, upload the “ShareflexContract” folder from the archive as well.

Open the Provisioning customer by navigating to the Shareflex Online app (remember the link in the settings menu?) and clicking on “Open Web IDE” under “Tools”.

Open the ShareflexContract > BEEML folder within the downloaded archive, then copy the contents inside file “0 Init.beeml”.

Head back to the Provisioning customer and replace the default script with the script you just copied. Perform a Precheck, then Execute it if no problems were found.

Open the Joblist and wait until the background job finishes. If no problems occur, the job’s Run State will be “Terminated (Normal)”.

Now, depending on what contract types you want to support, also execute scripts 1 to 8. Wait until each script finishes before starting the next one.

This is what your site’s homepage will look like after installing the Service Agreements contract type (script “1 DV – SA.beeml”):

Example: deploying the TimeKeeper app

The TimeKeeper app can be deployed as subsite on any of your existing (Shareflex-enabled) sites. It does not need its own dedicated site.

Needed role: Site (Collection) Administrator

Unzip & upload the provided TimeKeeper deployment package to the Deployment library of the Shareflex Core subsite:

https://<TENANT>.sharepoint.com/sites/<CREATED-SITE>/pscBAF/Deployment

Head to the Provisioning customer by navigating to the Shareflex Online app  (remember the link in the settings menu?) and clicking on “Open Web IDE” under “Tools”.

Locate the file “setup.beeml” within the TimeKeeper deployment package, open it with the text editor of your choice, then copy its contents.
Head back to the Provisioning customer and replace the default script with the script you just copied. Perform a Precheck, then Execute it if no problems were found.

Open the Joblist and wait until the background job finishes. If no problems occur, the job’s Run State will be “Terminated (Normal)”.