Chris_Hackett

[askCA TRANSCRIPT] CA PPM – April 12, 2018

Discussion created by Chris_Hackett Employee on Apr 16, 2018

Miss the April PPM askCA - Online Chat? Check out what you missed below and be sure to join us in May for the next session!

 

04/12/2018 10:00:18 AM from Chris Hackett (CA) to Everyone: Hi Everyone - We'll be starting in just a few minutes.
04/12/2018 10:03:43 AM from Chris Hackett (CA) to Everyone: OK Let's start!
04/12/2018 10:03:54 AM from Chris Hackett (CA) to Everyone: Ready for questions
04/12/2018 10:05:49 AM from Chris Hackett (CA) to Everyone: Quiet group...unless everyone is madly typing questions...
04/12/2018 10:07:36 AM from Chris Hackett (CA) to Everyone: Well this might be a short session. Any questions for us folks?
04/12/2018 10:09:25 AM from Julie Whitney to Everyone: do you have best practice guidelines for baselining projects?
04/12/2018 10:11:41 AM from Julie Whitney to Everyone: We were informed that the maximum number of custom attributes that could ETL to the Data Warehouse is 100. What happens with custom attribute 101?
04/12/2018 10:11:55 AM from Sarmistha Purkayastha (CA) to Everyone: @Julie: here's a link to some documentation that you may find useful: https://docops.ca.com/x/XN48Gw
04/12/2018 10:13:39 AM from Lynn Harris to Everyone: are there any published solutions/examples on how to use the links to easily navigate between the new UX and the classic? I was told "links" was a way to ease the navigation troubles, but I would hope it is not expected for users to setup a link to mulitple subpages for mulitple projects. Is there some "dynamic " way.. or any other suggestions to improve navigation between new and classic? I did not see anything in the documentation, but I could have missed it
04/12/2018 10:14:27 AM from Nick Darlington (CA) to Everyone: @Julie: The number of custom attributes is a per-object limitation (not total) and whilst it impacts ETL/Date Warehouse, it is not the only place impacted. 100 is given as a guideline maximum for consistency in performance as well as behaviour. When you go above this you may (or may not) run into issues as it starts to depend on various factors like the type of attributes, the DBMS vendor limitations, and so on.
04/12/2018 10:16:27 AM from Damon (ca) to Everyone: @Lynn specific sub-objects cannot be linked but you can create a link from Classic to the New UX as documented here: https://docops.ca.com/display/CCPPMOD154/Getting+Started+with+the+CA+PPM+New+User+Experience#GettingStartedwiththeCAPPMNewUserExperience-CreateaMenuLinkinClassicPPMtotheppmnew (hope that helps!)
04/12/2018 10:18:10 AM from Nick Darlington (CA) to Everyone: @Julie: I posted a small plea about this at the end of February: https://communities.ca.com/thread/241793180-please-do-not-create-too-many-custom-attributes-per-object
04/12/2018 10:18:59 AM from Julie Whitney to Everyone: does the new UX for resource management yet allow PMs to approve resource time recorded against their project?
04/12/2018 10:19:21 AM from Julie Whitney to Everyone: Note: the PM is not the Resource Manager.
04/12/2018 10:20:01 AM from Lynn Harris to Everyone: @Damon - I am refering to the LINKS feature, not setting up the link to access new vs classic. that link takes me to a document about configuring the new UX via actions, which we know to do. The "links" feature in the new UX - I had been told at CA world this would help with the navigation and to date I haven't figured out how
04/12/2018 10:20:03 AM from Neetu to Everyone: Does the mobile app now provides features to adjust submitted timesheet from prev weeks
04/12/2018 10:21:57 AM from Damon (ca) to Everyone: @Lynn -- thank you, yes, you could copy links from classic project pages and paste them into the new LINKS feature (sub-page in Projects of the New UX). As long as users have access rights they can use those links.
04/12/2018 10:23:10 AM from Julie Whitney to Everyone: @Nick, thank you.
04/12/2018 10:23:24 AM from Kathryn Ellis (CA) to Everyone: @Julie - any user with Timesheet Approval rights can approve a resource's timesheet in the new UX. The functionality has not changed from Classic to new UX.
04/12/2018 10:23:46 AM from Lynn Harris to Everyone: @Damon, ok so that goes back ot the user doing it, which is not feasible when a PM has 20 projects and on each one of them needs to acces say 3 pages.. that is 60 links to create??
04/12/2018 10:25:44 AM from Kathryn Ellis (CA) to Everyone: @Lynn - the user does not need to create additional links - When the user is in a current project and clicks the 'Classic PPM' menu link it will go directly into Classic for that specific project and from there they can navigate through all the subpages within Classic as they would normally do.
04/12/2018 10:26:44 AM from Julie Whitney to Everyone: @Kathryn. That's not my understanding of the new UX. I was informed that Resource Managers only have the ability to approve their resource timesheet line items in the new UX. If the scenario is as you describe then happy dance.
04/12/2018 10:26:48 AM from Kathryn Ellis (CA) to Everyone: @Neetu - the Mobile Timesheet application is only for approvals.
04/12/2018 10:27:55 AM from Neetu to Everyone: @Kathryn. No it is also for filling and submitting time along with approving
04/12/2018 10:28:42 AM from Kathryn Ellis (CA) to Everyone: @Julie - the default list of people is where you are the resource manager, however you can change the filtering to pull up any person for which you have approval rights.
04/12/2018 10:28:47 AM from Lynn Harris to Everyone: @Kathryn.. hey Kathryn!! yeah but the problem is that the link does not "follow" you. You must keep clicking it. If I have project A open, click Classic and do whatever, then go back to "new" to access Proejct B.. the user must click the classic again.. it does atuomatically have B open in Classic. Our users would end up having tons of windows open -- just overall the navgiation is still a hurdle (since 15.2 feedback) - an dour users have voiced that it is a roadlbock for them to use the new UX. So we are trying to find the easiest solution for navigation. These users run many projects.
04/12/2018 10:29:29 AM from Julie Whitney to Everyone: Under what circumstances would autoscheduling a project cause spinning (not doing anything)? What should we be checking?
04/12/2018 10:29:29 AM from Neetu to Everyone: My question however: if we can now adjust/return submitted timesheets from prev week?
04/12/2018 10:30:19 AM from Kathryn Ellis (CA) to Everyone: @Lynn - I understand. This is how the application is designed.
04/12/2018 10:30:51 AM from Kathryn Ellis (CA) to Everyone: @Neetu - checking
04/12/2018 10:30:55 AM from Lynn Harris to Everyone: @Kathryn,, yeah I know. I was hoping by now someone had come up with some magical work around.. thanks
04/12/2018 10:33:33 AM from Damon (ca) to Everyone: @Neetu Sarmistha will be sharing a docops page but A submitter can only return a timesheet for the current period. And, the timesheet must be in submitted status.
04/12/2018 10:33:52 AM from Sarmistha Purkayastha (CA) to Everyone: @ Neetu, here's a link to the Mobile Timesheet app documentation for your reference: https://docops.ca.com/display/CCPPMOP154/CA+Clarity+Mobile+Time+Manager+App
04/12/2018 10:36:13 AM from Nick Darlington (CA) to Everyone: @Julie: For autoscheduling not completing issues, you will likely need to raise a support ticket and can be looked at on a case by case basis. One thing you can check is if the 'job' to do the autoschedule has been created and running, it should list itself like any other job in the system - it's just that you initiate it from a different part of the UI.
04/12/2018 10:38:46 AM from Julie Whitney to Everyone: @Nick, Thank you. I will check that we have the noted job running first before we log a support case ticket.
04/12/2018 10:39:20 AM from Chris Hackett (CA) to Everyone: OK Everyone - We'll wrap up for today. Thank you for participating and join us back here in May!
04/12/2018 10:39:34 AM from Nick Darlington (CA) to Everyone: @Julie: The job should normally complete very fast and not be a long running process, so even if it's running, it could be an issue, but it changes where we would look for the cause.. job running = background service issue, job not scheduled may = app service issue
04/12/2018 10:39:51 AM from Chris Hackett (CA) to Everyone: Thanks again everyone!

Outcomes