Replies posted by Mathias Dahl
> ...you see all documents that have been attached by anyone, even when they do not relate to expenses.That's how it is supposed to work. Attachments / Documents is a generic functionality that works more or less the same way regardless of which screen you are in/on. "The system does not know" that is should only show ... well, what documents should it show, if you were to decide? How should it know to only show certain documents?As Robert said, you can use Restricted Access to completely hide documents from users that does not have access to it. It might solve the problem, or not, depending on how you set up the access on your documents. I would advice against it though, if the scenario above is the sole reason for implementing it. Using Restricted Access might have performance impact, especially for people that need to "list documents".If you want to make sure a user is not connecting the wrong document to a certain screen, a custom event could stop that. If you really want to hid
As you found out, the Aurena Agent does not allow sending in the To/recipient. That could be added, in theory, but it's not there now.What you can do is to use the Aurena Agent to execute a Docman macro and have the macro open Outlook. It's much more involved (and a document must exist, since macros need a document to get attributes to be used in the macro), more setup is needed, but it can be done. If you want to try that, have a look at how we execute macros in Docman using the Aurena Agent.Good luck!
There is no standard functionality for that, but you can probably solve it by using a clever custom event and event action. You can keep dummy document classes that in turn keeps the access templates for each country, then have the custom event apply that instead of, or also, to the document after it has been created.The rest is left as an exercise to the reader :)Good luck!
We are on Apps 10 UPD 14 and one of our departments is using Aurena at the moment. We’re having an issue with the approvals panel. The notes get cut off. This field in IEE is 2000 characters long but when the step is approved in Aurena, you can’t see what the notes say. Is there a way to change this behavior? Can I modify the attachments pane approval tab to have the cards show custom fields? I’ve looked at this for a while and I can’t figure it out. Notes are cut off. Text does not wrap and once the step is approved, you can’t view the entire note. Hi,We have solved this in IFS Cloud, in two ways:1. We enabled the multiline property on the Note field in the card, such that longer texts wrap around. We had to set a limit on the number of characters to be disabled though, to not make the card grow too high. We set the limit to 200 characters there, would that work for you?2. We enabled/added a List mode as well under Attachmens / Approvals where you can get the Note field to open i
HI @MarkMr That API seems to be used only for entering document texts typically using an assistant/dialog in the web client. You get a “resource not found” since the data (document text in this case) is only stored temporarily until the Finish/Ok button is clicked in the client. @Mathias Dahl any thoughts about an API to get the required information here? Regards, /Rifki I'm assuming you think this is in Docman. It is not 🙂My advice is to use Chrome's Dev Tools and then click the Network tab. Then load any page that has document texts on it. One of the svc calls will be the one that retrieves the text. Since I don't work with Customer Orders I would not know how to test this myself.
If you open Chrome's Dev Tools and keep the Network tab open you will see everything that is sent when the Aurena client does a media item upload. Did you try that, to see what headers it sets and what the values are?
Thanks for explaining. Since manufacturing is not my area of expertise I don't understand the flow fully, but my naive observation is that something is not right when the system presents an obsolete document revision to the user. Unless they are explicitly looking at an old SO or other old object or explicitly searching for it.When the user gets that warning, I assume they close that dialog and try to find the most recent revision. How do they do that? Or what other action to they take based on the warning?
No plans, but it could be something we need to do as password requirements are getting more and more strict. The problem with changing the algorithm however is that existing ones might be invalid, if we are not careful.How long are the passwords and what are the requirements in your case? I could experiment and see if I can do some recommendations to keep it within the limit of what the algo can handle…And, by the way, the problem could be something else entirely too…If you are willing to do so, you could send me an example password privately, once you changed it and I can have a look that way too,
Our data model supports any number of files to be stored against a document revision, even multiple files of the same type. There is however no user interface support and functionality that uses the capability fully more than the original file + view copy scenario.So, even if the data model supports what you want to do, you cannot do it today without a customization of the client.I would recommend you use document structures and/or sheets to keep multiple files against the same document.What is it that you are trying to achieve?
It should still be honored, but we had a bug where you could not create such a record, which is fixed now (not sure on which track though).Are you sure the wildcard is not honored if the status is Generating? That's a big that should be reported, if it is the case.
I tested releasing functionality with IFS Cloud 22r1 and the radio button appeared when releasing every third revision. Is this known issue? I cannot remember having that reported. If you like, file a support case and we will have a look.As for your original question, if you want previous revisions to be obsolete when a new one is created I think a custom event is your only option.For our learning, what is the larger use case here?
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.