Opening document dialog using soprotocol on company entity level broken since 10.3.8

lock
push_pin
done
Besvarat
6

Hi,

We use the following soprotocol to open a newly created document from a task menu:

soprotocol:document.details?document_id=<document id>

Now that customers have been upgraded to 10.3.8, we gotten reports that the above soprotocol does not work anymore on company level.

Exactly the same soprotocol does work on project level. (You can reproduce this by creating a button in the screen designer that executes above soprotocol on company level and project level)

For both company and project level I did notice that the following console message is logged when executing the soprotocol:

Are we using the wrong soprotocol here? (I also tried main instead of details, no change), or is this a bug that was introduced during the work for the SCILified document dialog?

 

4. sep. 2024 | 12:22 em

Allt Svar (6)

We are investigating this. Sorry for any inconvenience. 

5. sep. 2024 | 07:50 fm
Thanks, please let us know if/when there is Bug ID which we can communicate to customers.
5. sep. 2024 | 10:28 fm

BUG ID: 63033

5. sep. 2024 | 11:48 fm
Sadly not public (yet)
5. sep. 2024 | 11:54 fm
Public now and marked as fixed for 10.3.9. Can confirm it is fixed in my SOD tenant.
10. sep. 2024 | 12:14 em

I have problems with this in 10.3.11. A command below worked nice before - populating the dialogue with the correct company and template - allowing the user to fill inn information and create the document. Now the Company card changes to the specified contact_id, but the document-dialogue comes up with an existing document (the current I guess). 

The link we are using is: 
https://online3.superoffice.com/Cust0000/default.aspx?document.main[mode=new&edit=true]?document_id=0&contact_id=27130&person_id=32486&doctmpl_id=187

Is this another problem - or was it not solved. If there is required to change the URL - please advise me. 

12. nov. 2024 | 10:46 fm

Lägg till svar