It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,883
×6,033
×30
×19

question asked: Jan 14 '16, 4:33 a.m.
question was seen: 2,479 times
last updated: Jan 14 '16, 4:33 a.m.

Related questions

Why does the MSSCCI sometimes put automatically a green tick on Rhapsody packages?

0
Geoff Binns (30●6●25) | asked Jan 14 '16, 4:33 a.m.

MSSCCI sometimes puts automatically a green tick in front of a package that has not been checked-out (not locked under RTC). I suppose it concerns RHP dependencies between packages that RTC detects as a modification.

It may occur if the timestamp in packages have been updated even though the package may not have changed.

It means that we cannot trust the MSSCCI to know which files are locked or not. We have to go to the RTC client.

What is the correct process to adopt? Do we have to ignore/undo these false modifications? Do we have to include them in a Change Set?

Be the first one to answer this question!

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.