Analytics Information:We may directly collect analytics data, or use third-party analytics tools and services, to help us measure traffic and usage trends for the Service. These tools collect information sent by your browser or mobile device, including the pages you visit and other information that assists us in improving the Service. We collect and use this analytics information in aggregate form such that it cannot reasonably be manipulated to identify any particular individual user. Log file information is automatically reported by your browser or mobile device each time you access the Service. When you use our Service, our servers automatically record certain log file information. These server logs may include anonymous information such as your web request, Internet Protocol (“IP”) address, browser type, referring / exit pages and URLs, number of clicks and how you interact with links on the Service, domain names, landing pages, pages viewed, and other such information.
Device Identifiers:When you access the Service by or through a mobile device (including but not limited to smart-phones or tablets), we may access, collect, monitor and/or remotely store one or more “device identifiers,” such as a universally unique identifier (“UUID”). Device identifiers are small data files or similar data structures stored on or associated with your mobile device, which uniquely identify your mobile device. A device identifier may be data stored in connection with the device hardware, data stored in connection with the device’s operating system or other software, or data sent to the device by Stralto. A device identifier may convey information to us about how you browse and use the Service. A device identifier may remain persistently on your device, to help you log in faster and enhance your navigation through the Service. Some features of the Service may not function properly if use or availability of device identifiers is impaired or disabled.
Location Data:When you access the Service by or through a mobile device, we may access, collect, monitor and/or remotely store “location data,” which may include GPS coordinates (e.g. latitude and/or longitude) or similar information regarding the location of your mobile device. Location data may convey to us information about how you browse and use the Service. Some features of the Service, particularly location-based services, may not function properly if use or availability of location data is impaired or disabled.
Commercial and Marketing Communications:We use the information we collect or receive, such as your email address, to communicate directly with you. We may send you emails containing newsletters, promotions, and special offers. If you do not want to receive such email messages, you will be given the option to opt out or change your preferences. We also use your information to send you Service-related emails (e.g., account verification, purchase and billing confirmations and reminders, changes/updates to features of the Service, technical and security notices). You may not opt out of Service-related emails. You may also be able to be “found” on Stralto based on information that you provide (see “Find friends on Stralto”) above.
Import the Solution File into your Dynamics instance.
Open the StraltoDMX solution.
Click on Configuration and then “Signup for DMX”
Select the number of users and proceed to Checkout.
DMX comes with a 60-day free trial and your credit card will not be charged till the trial expires. You can easily cancel the subscription by using the manage subscription button.
Close the dialog. Now you can copy the DMX key and use it for your DMX Configuration.
If you ever need to regenerate the key you can come back here and do that. Don’t forget to update the key in the DMX Configuration after you do so. You can also manage your subscription from here.
If not already there, from within the solution select the DMX Configuration Entity and Add it to one of the menus e.g. Settings and Save
Go to Settings and Select “DMX Configuration” from the Menu.
Create a New DMX Configuration by clicking on +NEW.
Select DMX Type and then fill in the necessary information based on the type you select and save the record.
Azure Blob Storage
SharePoint Online- with or without SSI (Server-Side Integration)
Dynamics 365 Annotations
For Image Auto-tagging
Enable the Azure OCR Authentication Key. DMX can utilize Microsoft AI Cognitive Services to find keywords in images and auto-tag them.
To enable this feature, sign up for a cognitive services subscription on Azure and add the provided key to the “Azure OCR Authentication Key” field. DMX will automatically start auto-tagging your documents based on the auto-tags provided.
For Configuring the Portal
Enable the Microsoft CRM Portal. The following fields need to be filled out to have DMX enabled for the Portal. Further configuration of Portal is discussed in the Portal Section.
Dynamics Admin Username
Dynamics Admin Password
Dynamics Azure Active Directory App Client ID
Dynamics Azure Active Directory App Client Secret
Dynamics Azure Active Directory App Tennant ID.
Add DMX to the entity by clicking + on Entity Configuration. The entity needs to have Document Management Enabled. You can set that in Entity Settings.
This is where you can further customize the DMX experience:
Select the theme
Max upload size
Select fields you want to see on the DMX Client.
Click on + to add Required Document Types and sub document types.
You can control some important aspects of DMX from here.
Show in Portal- Allows you to control what types of documents should be shown and be available for upload in the portal
Track by Stage- Allows you to filter and sort documents by what stage they are connected to.
Filter by Role- Allows you to filter the document type and only show it to users with a role.
Auto-Tagging and Custom Fields
Auto-Tagging feature: automatically checks for keywords when a document is uploaded.
Custom fields of Text:
Options or Date type can be used to track additional structured data for a document.
Next step is to edit the form for the entity and add a web resource to the bottom of the form.
The web resource should point to stralto_dmclient.html and should be named “WebResource_dmclient”
Make sure to add the web resource in a separate tab and make it 40 lines, expandable and without border to get the best user experience.
For Portal, follow the same steps for the entity form but point the web resource to stralto_dmportalclient.html and name it “WebResource_dmportalclient”
Once you save and publish, you can just go to the entity form and start using DMX to upload and tag files.
CRM Users need to be part of the DMX Users Security Role in order to use DMX. DMX Administrator role is required to delete documents in DMX.
In Dynamics CRM
In Microsoft CRM Portal