Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X
After installing CWC 9.5.0 Work Order Utilities cannot seen in configuration. Kindly check attached image
Solved! Go to Solution.
@KG_96 I just checked the code, and it looks like the extension does not have any specific dependencies on 9.5.1. You can try importing it to 9.5.0, i just did not test it on that version.
Quote: "After importing and deploying the PTCSE.WorkOrderUtilities Building Block, users with the right permissions (see Access Control page) can access the user interface through the Configuration menu context in the ThingWorx Applications".
where I get PTCSE.WorkOrderUtilities Building Block
You can find "ThingWorx Applications Work Order Utilities Installation Guide" in attachment.
still not getting .....where I get Work Order Utilities zip file. I am using CWC 9.5.0 version
@SebB can you please check this?
(he is the one who made the extension, and I think he said we needed to reach him personally to get a copy but I can be wrong on that)
I know version 1 was shared on the forum last year (click link) but I'm pretty sure this is an old version that' probably not compatible with 9.5.0.
Attached you can find the latest version (v2.5) of the Work Order Utilities for CWC.
Please note that this version requires the latest version of CWC (v9.5.1).
If you are running v9.5.0 you have to upgrade to v9.5.1 first before importing the Work Order Utilities extension.
I also attached, the newest version of the User Guide and the Installation Guide.
The Work Order Utilities is not an official extension from PTC, there for PTC does not provide any technical support on this extension.
Hello SebB
Does this extesion will also work on 9.6 version ?
I have not tested the extension on 9.6.0 or 9.6.1 but based on the release notes of 9.6.0 and 9.6.1 it should be working fine.
Thier were no changes to the Endpoints or the Work Order data model in those releases.
However, in 9.7.0 are bigger changes coming with Route Versioning and Work Order management.
For this release I am planning some updates on the extension after the release is available.
Hello Seb,
I tried the extension in 9.6.1 and found a bug. I am sharing it just to enhace further product development of this utility.
On the Single create work order page, once you pop the window to select the product. The product is non selectable.
Thanks for letting me know, i will look into this issue.
In the meantime, you can try using the drop-down product selection instead of the advanced popup selection. For a small number of products this selecting is easier to use anyway.
In Composer navigate to the "PTCGPX.WorkOrderUtilities.Manager" thing and select the Configuration tab. Find the "AdvancedProductSearch" configuration and uncheck the checkbox, save the manager thing after. (See user guide page 7 and 15)
Thanks @seb
That worked well.
I am also facing another issue related BOM being not visible even after gettng a success message on OOTB ImportBOM_END service. As a result, I am not able to find the BOM in the Work order utility. Do you know of any reasons ? or maybe where in the UI, I can locate all the BOM's
{
"BillOfMaterialList": [
{
"ProductName": "PM3-100",
"Enabled": true,
"Description": "PM3-100_BOM",
"Items": [
{
"ProductName": "P-001",
"UnitOfMeasure": "EA",
"Quantity": 1,
"ScrapFactor": 0
},
{
"ProductName": "P-002",
"UnitOfMeasure": "EA",
"Quantity": 1,
"ScrapFactor": 0
},
{
"ProductName": "B-001",
"UnitOfMeasure": "EA",
"Quantity": 1,
"ScrapFactor": 0,
"Substitutions": [
{
"ProductName": "B-002",
"ProductTypeName": null,
"FactorOfConversion": 1,
"UnitOfMeasure": "EA"
}
]
}
]
}
]
}
. I am attachng the jSON as above and also the status message:
Can you please try executing the "GetBillOfMaterials" service on the PTC.SCA.SCO.DefaultProductManager thing, to double check if the BOM was created successfully.
I am getting no data.
I am still puzzled then why the importBOM service shows success message.
Check the PTC.FSU.CORE.Process.ProcessQueue_TM timer thing and make sure you have the TriggerUpdateQueueConfiguration_PRC, TriggerUpdateQueueNotification_PRC & TriggerUpdateQueueEventBased_PRC subscription enabled.
How the endpoint work is, when you execute an endpoint service for Work Order or BOM import, the service adds the request to a queue and the timer processes the queue every 60 seconds. The result of the endpoint service only indicates that the validation and adding the request to the queue was successful.
See ThingWorx Apps 9.6 - Endpoints - Help Center
Thanks for the detailed explanation.
The subscriptions are disabled for me. I tried to enable them from the UI but no checkbox is there. Then I tried to enable them usng the service EnableSubscription by passing the subscription name in the argument. However, the service returns no results. Is there a specific way to enable these subscriptions.
This worked after a few refreshes. Now the subsciptions are enabled.
You can enable/disable the subscriptions in the UI as well. See screenshots below.
Now that the subscriptions are enabled check if the BOM was created, they should also appear now in the Work Order Utilities UI.
Hello @KG_96
It looks like you have some responses from some community members. If any of these replies helped you solve your question please mark the appropriate reply as the Accepted Solution. Or if you found a solution on your own, please document it in your topic and mark it as accepted solution. This will surely help other users who may have a similar question.
Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.
Thanks,
Community Moderation Team.
Can you send files which support to V 9.5.0.Because we have just now upgraded from 9.3 to 9.5. It's difficult to further upgradation.
@KG_96 I just checked the code, and it looks like the extension does not have any specific dependencies on 9.5.1. You can try importing it to 9.5.0, i just did not test it on that version.
Ok. Thank you.It was working.