Workfront Calendar Visibility Issue

Workfront Calendar Visibility Issue

Category

Adobe Workfront – Calendar Management

Affected Role

Workfront Administrator

Priority

Medium

 

1. Issue Description

 

A Workfront administrator who originally created several calendars has left the organization and their user account is no longer active. Other administrators are unable to find some of those calendars in the calendar dropdown list.

Symptom

Calendars missing from the calendar dropdown for other administrators

Trigger

Original calendar owner's account was deactivated after leaving the organization

Impact

Calendars are inaccessible to the remaining team, disrupting scheduling and planning workflows

 

2. Root Cause

 

The original administrator did not grant other users or administrators access to the calendars they created. In Workfront, calendars are private by default. When the calendar owner's account was deactivated, the calendars became inaccessible to all other users.

Key contributing factors:

•       Calendars in Workfront are owned by the creating user and not shared by default.

•       Deactivating a user account removes their ability to manage their own resources, and no automatic transfer of ownership occurs.

•       Other administrators had no prior access or visibility into these calendars.

3. Resolution Steps

 

Follow the steps below to restore access to the missing calendars. These steps must be performed by a current Workfront system administrator with access to the Adobe Admin Console.

Step 1: Reactivate the Former User in Adobe Admin Console

1.    Log in to the Adobe Admin Console at adminconsole.adobe.com.

2.    Navigate to Users and search for the former administrator's account.

3.    Reactivate the user account so the account becomes active and accessible.

4.    Confirm the account status is active before proceeding.

⚠  Note:

Reactivating the user account is temporary and solely for the purpose of transferring calendar access. The account should be deactivated again after completing Step 3.

 

Step 2: Log In as the Former User


6.    use the "Log In As" functionality from the Workfront System Admin panel to impersonate the user.

7.    Navigate to the Calendars section to confirm the missing calendars are visible under this account.

Step 3: Grant Access to the Calendars

8.    While logged in as the former administrator, open each of the affected calendars.

9.    Open the calendar sharing settings (Calendar Actions > Sharing).

10. Add the appropriate administrator(s) or user groups and assign Manage access permissions.

11. Save the sharing settings and verify the calendar now appears for the target administrators.

Step 4: Deactivate the Former User Account Again

12. Return to the Adobe Admin Console.

13. Locate the former administrator's account and deactivate it again.

14. Confirm the account is once again inactive to maintain security and license compliance.


Comments

Post a Comment

Popular posts from this blog

Error: Number of included segments do not match

Introduction In this blog, we tackle a crucial issue encountered during the reprocessing of an X12 EDI message. We will get into the root cause of the problem and provide you with a solution to overcome it. Error: An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:       Error encountered during parsing. The X12 transaction set with id '103465910' contained in functional group with id '02', in interchange with id '000000009', with sender id '4532345856     ', receiver id '8038025150     ' is being suspended with following errors: Error: 1 (Miscellaneous error) 4: Number of included segments do not match . The sequence number of the suspended message is 1.  Root Cause: The issue stems from a mismatch in the number of se...
Read more

REST API Calls with Query Parameters in BizTalk: A Step-by-Step Guide

Image
 Introduction In this blog, I will provide a comprehensive guide on how to call a REST API that requires query parameters. We'll walk through the necessary steps to set up the environment and make successful API calls. Solution High Level Steps 1. API Overview: We will be using an open API for demonstration purposes. The API endpoint we'll be working with is: https://randomuser.me/api/?results=1 2. Schema Creation: Create a schema named "SourceA" that matches the structure of the messages you'll be dropping in the receive location. To create a JSON response schema, follow these steps: capture the JSON response by running a test in Postman, and then utilize a JSON schema generator to create the desired JSON schema. 3. Field Promotion: In the SourceA schema, promote the field called "results." This field will serve as the variable for the query parameter. 4. Receive JSON Pipeline: Develop a receive JSON pipeline that can receive JSON messages and convert t...
Read more

Updating BizTalk SSO DB using BTDF and a simple BTDF deployment

Image
Introduction In some cases, it becomes important to securely store key-value pairs, such as configuration data (e.g., usernames and passwords), rather than hardcoding them within a BizTalk orchestration. One effective way to achieve this is by storing these key-value pairs securely in the BizTalk SSO (Enterprise Single Sign-On) database and subsequently reading these values within our orchestration through a simple line of code within a BizTalk expression shape. In this blog post, we will go through the steps to add key-value pairs to the SSO database using the BizTalk Deployment Framework (BTDF). We will also explore how to read these values within a BizTalk orchestration and perform a simple BizTalk deployment using BTDF. Steps Creating a BizTalk Solution, Schema Project and Map project: Let's first create a BizTalk Solution called "SSOPOC" and a project called "SSOPOC.Schema". For this, you need to go to Visual Studio and click on File --> New Project --...
Read more