Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Behavior changes coming in Workspace ONE Content 5.0 (78206)

Last Updated: 4/24/2020Categories: InformationalTotal Views: 4629Language:
JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Purpose

Workspace ONE Content 5.0 will be the first version of Content to use the Workspace ONE SDK on Swift. Previous versions of Content used the Objective-C version of the Workspace ONE SDK. With this architectural change there are a few behavior changes administrators should be aware of as they may impact behavior that end users are accustomed to.

Resolution

Content Legacy Settings will be deprecated.

Workspace ONE Content will no longer support the Use Legacy Settings and Policies configuration setting under System Settings > Content > Applications > Workspace ONE Content App.

The assigned SDK profile will now be the supported mechanism for delivering DLP policies to the Content app.

Action Required

If Use Legacy Settings and Policies is enabled, ensure that the default SDK DLP policies match to prevent a change in end user behavior. These settings can be found under System Settings > Apps > Settings and Policies > Security Policies.

Additional updates to existing app behaviors as part of the upgrade to Content 5.0

The logout function while in standalone mode will no longer be supported. In place of the logout function place users will have the option to unenroll.
Note: This scenario and only occurs for configurations where the SDK setting for Authentication Type is set to disabled.

Work offline option on the username/ password screen is no longer supported. The only way a user can work offline is by going to App Settings and then enable Work Offline.
Note: Even in this case network calls will still be made and offline work will only be honored by the Workspace ONE Content specific interactions only.

Data Loss Prevention: If Allow open in white-listed apps is enabled and a user attempts to open content into a non-whitelisted app, then an error will be displayed stating that this is not allowed. The more options view will also now be dismissed.

If there is a wipe performed, for instance a user has reached max number of passcode attempts, the app will no longer automatically flip to Intelligent Hub. Users should leverage Intelligent Hub to reestablish trust with Workspace ONE UEM and the Workspace ONE SDK single sign on setting to regain access to Content.

Workspace ONE SDK authentication screens are updated to a new user experience.

If the Workspace ONE SDK fails to fetch content settings after launch, the user is now presented with a failure message explaining that setup of the application has failed.

If using the forgot passcode workflow, the same username must be used to reset. If a different user needs to login, the application must be wiped via enterprise wipe.

Clipboard changes:

The copy-paste restriction is dependent on two flags now (copy in and copy out):

Copy in - copying something outside the app and trying to paste inside.

Copy out - copying something inside the app and trying to paste outside.

Generate Link flow and Copy Logs flow are updated:

Previously this function was not impacted by clipboard restrictions. We will now enforce restrictions on link generation and copying of logs.

Post Upgrade:

The Content app will be hang on the splash screen until it detects a network connection. The application needs to be online for first launch.

There is a new feature in the Workspace ONE UEM Console called auto logout that applies to CICO use cases. Users will see that the app is locked after the auto logout period expires. The Content app will present a username and password prompt while Intelligent Hub will take the user to the group ID screen. The auto logout setting can be configured under Devices & Users > General > Shared Device.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workspace ONE

Related Versions:

Take Our Survey

Support Assistant