cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

WTDocument Soft Type Question(PDMLink 8.0 M040)

borourke
5-Regular Member

WTDocument Soft Type Question(PDMLink 8.0 M040)

We have always made available all of the OOTB WTDoucmnet soft types(Draft, Agenda, General,etc.) to our users. Most use General, and we control the various states through the associated LifeCycle, Some users have started to the the Draft soft type, and then want us to change the type from Draft to General after the document has been approved. We cannot seem to find a way to change to change the soft type from Draft to General. Our soluction will be to remove the Draft type and force the users to use only the General type. Does anyone know of a way to change the document type from Draft to General? Thanks in advance!
6 REPLIES 6

I know how, but it definitely wouldn't be a PTC supported customization. If
you wanted to capture the same data, after conversion, I would recommend
having similarly named soft attributes on each subtype though it is not a
requirement. You'll have to learn some SQL as there isn't an easy way to do
this within the Java API without customization. What you are trying to do
would be in the same respect of having an IBA value named XYZ as a string
and wanting to convert it to float value typed IBA. Let me know if you want
to discuss this more and go down this path. I have contemplated making a
utility for others to use in the past, but since I do not directly license
PTC software I do not know how they would treat reselling add on software,
so I have never tried.





HTH,

David DeMay







_____

Bill,

where would you want to change that? if from within your workflow it is
easy - this is in ext.tools.UpdateIBAs accessible via the "-t type-name"
option.
relevant code is
((Typed)pbo).setTypeDefinitionReference(TypedUtilityServiceHelper.service.getTypeDefinitionReference(type));
and later persist the obj.

if you need it from a GUI you'd have to create a jsp page and call it
from there - pretty basic too.

hth, martin

bill o'rourke wrote:
> We have always made available all of the OOTB WTDoucmnet soft
> types(Draft, Agenda, General,etc.) to our users. Most use General, and
> we control the various states through the associated LifeCycle, Some
> users have started to the the Draft soft type, and then want us to
> change the type from Draft to General after the document has been
> approved. We cannot seem to find a way to change to change the soft
> type from Draft to General. Our soluction will be to remove the Draft
> type and force the users to use only the General type. Does anyone
> know of a way to change the document type from Draft to General?
> Thanks in advance!
>

If the two types differ in their IBA's, This will mess up previous
iterations and the actual data in the IBA values previously captured.

setTypeDefinitionReference is perfect for creating a new document which has
not been defined yet, but reusing a previously subtyped object I'm pretty
sure would break any relationship in database for values stored in a
different IBA type.

It may be okay in this particular case since it is purely OOTB but off the
top of my head I do not know if there are subtle differences between the
OOTB types and their IBA's. Even if the IBA's are the same I don't what
impact that'll have on previous iterations...

Good luck...
David DeMay


hi,

imho an ibaholder just "holds" the ibas - no matter how these were determined. they may come from introspecting a type
definition and creating ibas that correspond to what ibas the typedef has, they may come (even additionally) from
classification, and you can put other ibas onto it as well. the update screen will render input fields for ibas present
even if they do not belong to the type definition.

there is however no guarantee that someone codes a piece of UI that assumes ibas are in sync with the type def, but I'd
consider that a bug then.

cheers, martin

David DeMay wrote:
> If the two types differ in their IBA's, This will mess up previous
> iterations and the actual data in the IBA values previously captured.
>
> setTypeDefinitionReference is perfect for creating a new document which has
> not been defined yet, but reusing a previously subtyped object I'm pretty
> sure would break any relationship in database for values stored in a
> different IBA type.
>
> It may be okay in this particular case since it is purely OOTB but off the
> top of my head I do not know if there are subtle differences between the
> OOTB types and their IBA's. Even if the IBA's are the same I don't what
> impact that'll have on previous iterations...
>
> Good luck...
> David DeMay
>
>
>

I have a tool (external) that can change a type. I can send on Monday.

Could you send java code for update soft type? Thanks.

Announcements
Learn more about how we are using our browser poll here