Can we create Physical objects through DFC

Hello All,

I have requirement to create the Physical objects through DFC . I am facing issue like after creating object I am unable to charge out the object through Library service of Records client.

I have applied the related aspects to physical object : dmc_prm_chargeoutable / dmc_prm_physical_proxy , those are getting applied successfully , after that i am able to make library request .. but I am unable to perform Charge out action on those Library request.

Can someone suggest, if I have to create physical object through DFC and make required actions available through RM client.. what all aspect or other things need to be taken care ?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Haroon_A

What's the error you get?

If I remember correctly, you'll need to set the is_available to true.

myPhysicalObject.attachAspect("dmc_prm_physical_proxy", null);

myPhysicalObject.attachAspect("dmc_prm_chargeoutable", null);

myPhysicalObject.setBoolean("dmc_prm_chargeoutable.is_available", true);

All comments

Haroon_A

What's the error you get?

If I remember correctly, you'll need to set the is_available to true.

myPhysicalObject.attachAspect("dmc_prm_physical_proxy", null);

myPhysicalObject.attachAspect("dmc_prm_chargeoutable", null);

myPhysicalObject.setBoolean("dmc_prm_chargeoutable.is_available", true);

Kothari

Thanks Ahmad .. I really appriciate your help dmc_prm_chargeoutable.is_availbale worked for me.

Here I am creating physical object thourgh DFC and I missed to set this attribute as true , Do you have any documentation or any details on these aspects related attributes infromation in detail.. I believe i may miss out / anyone when thry are creating obejcts through DFC.

I will be working on migration and creating these obejcts through DFC and you can understand if forget/miss to set any single required attribute I will miss the Records functionality.

Haroon_A

I don't have any documentations, unfortunately. But, here's an idea.

You can create a physical object (folder or document or container) depending what are you planning to migrate, in RMA, properly. Then, dump its properties, and verify which aspects and attributes are set. Then, try and populate the same attributes via DFC.

Just a tip: try dump your physical object in RepoInt, rather than iapi, because in iapi, you won't get the full name of your aspect.

Kothari

Thank you.. your tip was my next question :-)