Teamcenter Preference : Project Assignment

User Scenario : User was trying to assign the project to object in Teamcenter (Right Click -> Project->Assign) and he was able to assign it ,but when he checked the object  project property property was empty .

Solution : The issue was solved by editing the TC_Project_Validate_condition' preference value to 1

Preference Description :
TC_Project_Validate_condition default value 0

VALID VALUES

0  The system confirms the user is a privileged member of the
   project before allowing the user to assign/remove objects to/from    a project.

1  The system confirms the user is either a privileged member of
   the project, or that the user has the ASSIGN_TO_PROJECT
   privilege before allowing the user to assign object to a project.
   Likewise, a user must be either a privileged member of              the project, or have the REMOVE_FROM_PROJECT privilege to       remove an object from a project.

2 The system confirms the user is a regular project member and has     the ASSIGN_TO_PROJECT privilege before allowing the user to assign   object to a project. Likewise, a user must have the              REMOVE_FROM_PROJECT privilege to remove an object from a project.

3 The system confirms the user is a privileged member of the project   and that the user has the ASSIGN_TO_PROJECT privilege before      allowing the user to assign object to a project.Likewise, a user     must be a privileged member of the project and have the      REMOVE_FROM_PROJECT privilege to remove an object from a project.

Teamcenter WorkFlow : Create form and attach to root task

Problem Statement : Create workflow which will create form in Teamcenter and attach it to the root task and display it to user.

Here you will understand how OOTB handler can be used in the workflow for form creation and display...

Please follow the snapshot with details,it will help you to understand workflow and handlers use.

 - Available the workflow for use

 - Visible this workflow for some of user using Template filter

SUBMIT TO WORK FLOW : Create object for which workflow is available (Defined in previous snapshot (Object Type for which workflow will be avialable)).

- Submit object to created workflow

- Select the MY worklist and expand Task to Perform as shown in    snapshot

     

 - Select the task in the worklist and on the right side in viewer  tab you will see workflow process in process view as shown in snapshot

 - Select the form which workflow has created and check

 - You can checkout the form and modify it

 - Complete the task

-----------------------------------------------------------
This section is just for understanding what else you can do
- You can remove the form which you have created and attached .please refer the snapshot for the same(Argument value for handler is Form object class name)


- You can execute ITK code as well from workflow or some shell .Please refer below snapshot for the same

Teamcenter Workflow : Glimpse on workflow Important part

Teamcenter Workflow : Use Case

Scenario : Admin user were unable to see the reference attachment for workflow submitted task so that he can open and see the attached file.



We tried changing the 'EPMTask_PseudoFolder' preference Protection Scope value to 'Site' and it worked

Teamcenter SOA Client : Use case for BOM creation

Scenario : Create a BoM structure under multiple part revisions already existing in Teamcenter.(eg: Revision A and B already exist in Teamcneter and now creating bom under Revision A and then under revision B and so on )

Details :
We were trying to use the com.teamcenter.services.strong.bom.StructureManagementService API named addOrUpdateChildrenToParentLine.
This API tries to create the BOMView object per revision and hence worked for the first revision however failed for the next revision since the BOMView already existed.

This scenario was working fine in Teamcenter and we figured out that Teamcenter was calling a different API to create the BOM structure.
In the communication monitor we found the api named 'add' under class com.teamcenter.services.strong.structuremanagement.StructureService.


Other Way to handle scenario is to add the existing item bomview object to the CreateBOMWindowsInfo object when you create the BOMWindow.  Then it will not try to create another BOMView at the item level but just use the one provided.