Ideas Portal
The current integration with PressWise is pretty good. It handles many situation with ease. However, there are times where attributes supported by PressWise are ignored by Pressero. There are also some attributes that Pressero supports that are not documented.
The KB article located here: https://support.aleyant.com/kb/a841/how-does-data-in-pressero-map-to-data-in-presswise.aspx?KBSearchID=279709 shows the current attributes supported. However, I know that the workmode attribute under item is supported because I have a pricing engine using it and it flows into PressWise correctly. However the gripperSetting attribute is ignored when generating the XML for PressWise. That is critical to this product, since without it it fails to batch correctly in PressWise.
I am aware that I can likely create an APID in PressWise to address this issue. However, it does not solve the underlying problem in that Pressero simply ignores attributes that I put into pricing engines.
It appears that we are the only customer using the PressWise integration, or at least the only one experiencing issues with it.
Another pain point for us is the lack of full API support. A perfect example is a padded job. It appears that if Pressero encounters an attribute that it does not understand, it simply ignores it. This is less than ideal.
I have a pricing engine that is attempting to set presswise_padding to 50. However that does not come across in the integration. This is a supported field in the API, so there is no reason to discard it.
I would like to see many more fields supported in the API. As it stands now, I have to create a separate APID in PressWise for any order than requires padding. It has worked so far because every padded product we've added has had a fixed padding amount. However, we have a customer who is asking to add a padding option in the pricing engine to allow for different pad amounts. There is NO way that I can accomplish this with the current setup.
Please consider adding at least this field ASAP.
To add to this request, PressWise supports options for estimating tasks. Currently, Pressero has no way to pass these options on to PressWise necessitating the creation of APIDs to handle this when it comes up.
I propose adding the ability to pass the option for an estimating task. It should be fairly straight-forward. As simply as appending ":" + OptionID to the end of the pricing attribute. Then when the system is processing the attributes for injection, it could check to see if a pricing attribute has an option, and create the correct XML for injection.