Creating Template Tasks with Duration and Planned Hours Using Workfront Fusion

Introduction

Creating template tasks with duration and planned hours in Workfront can be a bit tricky. This article will walk you through the necessary steps to configure and successfully create template tasks with a duration of 1 day and planned hours of 2 hours.

Steps

1.       Drop a “Create Record” module in the scenario editor.

A screenshot of a logo Description automatically generated

2.       Choose the correct Workfront connection and select the Record Type as Template Task.

A screenshot of a computer Description automatically generated

3.       Under the fields to map check the check boxes:

·       Duration Type

·       Duration Unit

·       Duration Locked

·       Work Locked

·       Name

·       Parent ID

·       Role ID

·       Template ID

·       Work (This field represents Planned Hours)

A screenshot of a computer Description automatically generated

4.       Perform Field Mapping

·       Map the fields as per your requirements.

·       Ensure that both Duration Locked and Work Locked are set to Yes.

o   Note: This step is crucial. If these fields are not locked, the duration and planned hours will not be properly set.

·       Another important point: Planned Hours is represented by the field Work in the mapping section.

 

A screenshot of a computer screen Description automatically generated

A screenshot of a computer Description automatically generated

5.       After the running the scenario with this module, the template task will be created as shown below.

 

Comments

Post a Comment

Popular posts from this blog

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

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

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