Hi, another note from the documentation of Mathias (in addition to what already Damith said): header parameter ‘If-Match’ must be set to ‘ETag here’. Best regards, Heinz
Hi, all certificates can be downloaded from IFS’s Trust Center Trust Center - IFS Best regards, Heinz
Hi Yannick, just go to EDM Basics and set the extension ‘PDF’ to ‘Original’ instead of ‘View Copy’. Then the file planABS.pdf will be checked in as original and the xlsx won’t belong to the same document. Best regards, Heinz
Sure, this is possible if you set the ‘User Settings’. BR, Heinz
So it made me realize why you said there was no WSDL in App10 (or App9), because PL/SQL Methods Webservices is different thing (https://docs.ifs.com/techdocs/foundation1/050_development/024_integration/020_webservices/020_plsql_methods_webservices/default.htm). It required a bit of modeling, not only setting up routing. And it produced a WSDL too. It was not the PL/SQL method that generated a WSDL. And you will never be able to generate a WSDL file from the PL/SQL code.The WSDL came from the model. But you won’t have such a model in IFS Cloud. So, if it’s essential to have a WSDL file, I see 2 options:Create the WSDL file manually in any text editor Use any Apps 10 environment where you can create the model, generate the WSDL file and than just slightly modify it in a text editor. Best regards, Heinz
No difference in routing to Apps 10. Just create a routing address with type PL/SQL and then use this address in a inbound routing rule. Choose no queue (as it should be synchronous) and use a content based routing (e. g. check for existence of a special node). Best regards, Heinz
Sure it does. The PL/SQL method still must return a CLOB. That’s the synchronous response. Best regards, Heinz
You can still route incoming XML messages to a PL/SQL method. No change between IFS Applications 10 and IFS Cloud. Used it several times and still works fine.(WSDL was also not available in Apps 10 if you just implemented the interface via PL/SQL method.)Best regards, Heinz
Hi Magali, have you ever thought about object connection transformation? Here you could configure that all documents attached to the master part will also be shown at the purchase parts. (This even works for documents which were attached long time ago. So, it’s nothing which is triggered the the action ‘Create object connection’.)Only disadvantage would be that the document is not connected to the purchase part. So, if you would check the object connections for such a document you won’t see a connection to PurchasePart. Nevertheless, in the purchase part screen it will show the document. Best regards, Heinz
Hi,if you transfer a document from one LU to second LU via Object Connection Transformation, then this document is not attached to the second LU. If you check the tab ‘object’ in document revision you won’t see the second LU (because it’s not attached to this LU).And also if you deactivate the Object Connection Transformation you won’t see the document at the second LU any more as it was never attached.Best regards, Heinz
Not sure if ‘POST’ is correct. I would try it with ‘GET’.But this won’t change the problem that your authentication is wrong. IFS Cloud requires OAuth2.0. If you get a 401 error, there’s something wrong with your authentication. If you really got a token, you might got it from the wrong authentication server?
Please use https://<server>:<port>/int/soapgateway.Than you need a inbound routing rule for the message. (It’s no longer possible to cann the BizAPI directly, as we don’t have BizAPIs in IFS Cloud.And you will need a routing address (e. g. of type ‘Plsql’) that can handle the message.
I never used incoming routing addresses of type ‘Projection’. I always used ‘Plsql’ and created PL/SQL code that handles the XML document.Could it be that your transformer does not work as you expect? Just use a different routing address of type mail and use your mail address. Than you will see what would be sent to the projection. Probably it’s the wrong format for this projection.
Yes, IFS Connect can handle incoming XML files. I created several interfaces for IFS Cloud that handle incoming XML documents. Works fine.
You could create an insert script that creates the datebase task. Than you can deliver this insert script.
Hi Theo, please see IFS Report Rule - Check In To Document Management not uploading to shared Repository | IFS Community Report Rules will only work if using the database repository. Best regards, Heinz
Does the user which is used to authenticate in Postman have neccessary access rights to see the quotes? So, did you really run the select statement that return records as the same user?
IFS Document Management does not offer a possibility to set this value per user.But in Page Designer you can define default values for all fields. And there you can have one context per user and thus different default values for each user.
Hi Mathias,today I had a ession with the customer and the partner and they showed to me what they did. They create a document without attachment when the object is created. Via a report rule th printed document is attached to the existing document revision. Until there, everything works as described by you. But if we print the report a second time, we would have expected that a new document revision would be created. That’s how we understood your solution. Unfortunately that’s not the case.We see in report rule logs that the rule was executed. We don’t see any error message. But no document revision was created.Best regards, Heinz
Hi, I would assume that ‘DocReferenceObject’ is missing in the Service List for LU Shipment. Best regardsHeinrich
Hello Sayeef,for documents you can use any attachments as it can be configured in basic data.For media it’s exactly the list you see in the client when you choose the file.Best regardsHeinrich
Hi,that’s a differnt approach. If you use a callback function it won’t be synchronously.Best regardsHeinz
I did it several times with Plsql_Rest_Sender_API.Call_Rest_EndPoint3( rest_service_ => NULL, receiver_ => '<any_name_for_usage_in_routing_rule>', xml_ => json_, url_params_ => url_params_, http_method_ => 'GET', http_req_headers_ => 'Content-Type: application/json', query_parameters_ => query_params_); Variable ‘json_’ should be a CLOB containing the json document you would like to transfer. Variables ‘url_params_’ and ‘query_params_’ can be set as in asynchronous REST calls. Works fine. Best regardsHeinz
Hi Cindy, you can’t set an approved document to preliminary. So, you have to create a new revision if you would like to change this document. Best regardsHeinrich
Sure, that’s the main purpose of document macros.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
