Please do a repair. After installing you need to do a double repair, as mentioned at install doc. There should be an output, which you can accept and execute. Do another repair and verify, if the output is empty.
Afterwards that error should be gone.
sadly it is not supporting Sugar8. We are waiting for SugarCRM itself providing us an add-on integrator permission. Since we support similar SugarCRM frameworks such as Suite and Spice as well, its is more difficult. However, if there will be a client demanding sequencing add-on for Sugar8, the upgrade will be availbale.
There must be more than just a workflow action given. For running you also need to have certain conditions being successful. Actions can be only triggered after a condition matches. If you want to do sth at Lead status change, you will have to figure out your conditions and also check the the workflow setup.
For detailed support you can host a websession or record your setup and errors by video and send by e-mail.
it just support latest Sugar 6 standards as described in here. Sugar7 does not support old workflow chainings of logic_hooks. We got too much trouble by hosting the addon for Sugar7, thus we removed it from our support.
since I am not using any aow modules, I cant give you a satisfying answer. However, my plugin does use a logging table for triggered records, which got linked to any defined workflow. It is mandatory to log them, if you have a certain limit defined. For example I provide the feature that you can trigger workflow just one time (eg new record) and never again. Thus I need to store the record somewhere. Further, I do save the logged records, but only once it has been identified to trigger any linked action. Therefore it should produce way lesser overhead than aow modules, where they save all the time any interaction of any SugarCRM record.
not at all. You can have as many sequences as you want acting on different modules. There you are right, However, you sent me two different sequences and thats the actual problem. Somehow there must have been a previous one, which is interfering to the current one. The next value check uses always the same procedure within the column of a table. But if the setup changes and there are already older values given, you can face such problems. To solve it, you must repair the data by your own and reset the values. In any case, you should backup your table(s) before!
Well there were definitely two sequences defined. I guess that is the reason for your current issue. They have different length and different zero padding. Therefore it will always create one number and use it. To fix it, you must correct either the old wrong values from your table by hand, or you remove them and use autofill. Otherwise you can send me your table and sequence definition and I can try to repair by some sql commands, but that service would be paid in advance.
Sounds like there is permission issues going on. If a sequence is deleted, it is not triggered any more at your modules. Maybe it is linked to another user? You can check it by reading the table "sequences" If you dont want to use it, you can update the "deleted" flag to "1".
I try to reproduce the error, but I failed. Sadly there is no e-mail address given by you, thus I could send you a recorded video of my local trial. I used a fresh Suite 778 and my latest addon.
I can see, there is also a difference between your and my version, since you have two "1" images next to your auto filled field.
Ok, I understand. Did you actually upgraded to the latest version I have sent you few days before by e-mail? By trying your sequence out and some dummy date as C300 or C999 or C1000 I can't face any error. Duplicating works great and the readonly flag prevents any direct editing.
If the upgrade wont help, I guess, we will need to do a websession. I must have a deeper look within your application and check the database outputs. For that I would need direct access to your webserver for touching the existing files.
Can you have a look, if there is also a clients_cstm table available? Your sequence definition is not matching to the given table. The column of your export is called "anum", but the sequence is linked to "anum_c", which is usually a custom field stored at the _cstm tables for each module.