[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [plcs-dex] Template dependancies
Sorry Tim, I’m responsible for the
assigning_approval_person problem you have. I’m currently editing the
capability assigning_approval, and in doing so I thought that the name was
incorrect (approving person is more accurate than approval-person), and changed
it… Without thinking about consequences. I still think I made a change to the
better, but if consequences are too big and its not worth it, then I will
change back. Regardless of this specific case, I think
you are right in the need for visibility in DEXlib, because since templates are
quite new, I think we will bump into this type of issues several times more,
until the templates have settled down a bit. We are still learning all this… Peter Bergström From: Tim Turner
[mailto:tjt@lsc.co.uk] Hi,
I
completed several templates for (Variance v1.20) which call others (&
therefore, rely upon them) whose mapping paths were successfully parsed last
week - but now have errors in them. This
is because of changes in underlying templates from other (well meaning) editors
which have either removed certain parameters or removed whole templates
altogether - which were expected by those re-using them. While
fixes are a normal part of CM life, the impacts can be extensive if a template
has many dependants. It would be nice to somehow know when dependancies change,
and perhaps to know what templates will be affected when making changes: can
Dexlib provide such a view for developers/editors? I
will need to redesign my templates if assigning_approval_person is to stay
deleted - so some feedback on the status of this template would be useful. Perhaps
we should agree to "announce" such removals. Regards,
NB
- On a related issue: I think there are similar issues when reference data are
removed; the capabilities which were developed using them now have significant
'holes'. ************************************************************************* DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY
MARKED*** The information in this message is confidential and may
be legally privileged. It is intended solely for the addressee. Access to
this message by anyone else is unauthorised. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful. Please immediately contact the sender if you have received this
message in error. This e-mail originates from LSC Group. Registered in |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]