in NX Manager or for export ?

[Ehaviv]

Hi

Can someone explain this phrase.
Its seems like there are 3 possibilities
1 import
2 in nx manager
3 export

in NX Manager or for export

nput_part_name	Input	The name of a part in the current clone 
operation; for import, an O/S filename; 
in NX Manager or for export, a CLI name

UF_CLONE_set_item_type (view source)
 
Defined in: uf_clone.h
 
Overview
This routine sets the item type to be used for this part in the current 
operation. See UF_CLONE_ask_item_type for details of how this will be applied 

Environment
Internal and External 

See Also
UF_CLONE_ask_item_type 
UF_CLONE_set_def_item_type 
UF_CLONE_ask_def_item_type 
UF_CLONE_convert_cb_t 

History
Originally released in V16.0 
 
Required License(s)
assemblies

 
int UF_CLONE_set_item_type
(
const char * input_part_name, 
const char * item_type 
)
const char *	input_part_name	Input	The name of a part in the current clone 
operation; for import, an O/S filename; 
in NX Manager or for export, a CLI name
const char *	item_type	Input	The item type that should be applied to 
the part

 

[Ehaviv]

My question is

Is this function works only
For import and export and not
for cloning.

Thank you.

 

[NutAce]

A quick search resulted in the below explanation of the function.

uf_clone.h

To answer your question, Yes it can be used for Cloning, Export and Import of assemblies.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX12 / TC11

 

[Ehaviv]

Hi Ronald and thank you very much.

Can you post the link if you're searching.

 

[NutAce]

Can you post the link if you're searching.

I did...click on uf_clone.h


Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX12 / TC11

 

[Ehaviv]

Hi Ronald uf this is what about.
It says can be not must be.
Thank you.

uf_clone.h (view source)

Overview
This include file declares routines used for performing clone
operations and clone based PDM Assembly Import and Export
functions. Using these routines you can:

Clone an assembly

Edit an Existing assembly in place

Import an assembly to the PDM system

Export an assembly from the PDM system

Note that all these operations act on part files on disk, parts which
are currently loaded in the session will not be affected - if you wish
to operate on parts which have been modified in the current session
you should save them first.

It is also possible to register user supplied callback functions,
which clone operations will call at appropriate times. These functions
can be registered in for use in Interactive NX as well as in
Open API programs.

The callback functions are of two types:

Notify callbacks; these are called before and after actions are taken
during a clone operation. A callback called before the action is taken
has the option to forbid that operation from occurring. This could
allow enforcement of company practices or conventions. Notify
callbacks can also be useful to allow you to take actions which are a
part of your company processes when a clone operation is performed,
setting specific part attributes when a part is exported from the
NX Manager database for instance. Finally they can be used to provide
feedback to the user about the progress of the operation.

Convert Callbacks; these are called when NX requires a value
for a piece of information that has not been specifically supplied by
the user or program. They are called before NX goes on to
apply its own default algorithms for generating these values.

In both cases, multiple callbacks can be registered at the same
callback point - the callback lists are ordered, and callbacks earlier
in the list can allow callbacks later in the list to be called, or
prevent them from being so, by returning appropriate return codes.

can be used

Note on Nomenclature: because the functions and types declared here 
can be used both within NX Manager or outside it (when performing a 
clone), or both at the same time (when performing an import or an 
export),

there is a nomenclature problem. What NX Manager calls a part
'number', native NX calls a part 'name'. NX Manager has a database
attribute of 'name' which is not the same as the part number.

In this file, name is used throughout in the native NX sense,
corresponding to the NX Manager part number. The term 'pdm_name' is
used for the database attribute 'name'.

'def' is uniformly used in function names as an abbreviation for
'default', likewise 'co' for 'checkout'.