And because ScriptCase Tools is an extension intented to be used with ScriptCase, which is a paid software, it was not accepted as a listed add-on. The expected result should be as shown in. That means an extension can't be published (listed) in Firefox's "webstore" if it works together with a paid software, and although the add-on is digitally signed by Firefox's webstore, the file must be hosted by the owner/author. If the field is not enabled in your template, we need to follow the step by step below: 1 - Within the Login application in your ScriptCase, more precisely in 'UserHTML', we click on the Check button to verify the fields that are not included in the HTML template file located in the external libraries. Require payment to use core add-on features (upfront or after trial) In this case, we need to ask you to switch your add-on to 'unlisted' (=selfhosted) as the add-on requires a payment for it to be useful. It took 19 days to receive a response for the first publishing attempt:ĭoes this add-on only work with paid software? Currently to run these two reports the user has two buttons, one to run the pdf, the other to run the grid. The first I created in the scriptcase pdf generator, the second I created using the user-defined grid. All extensions are manually reviewed by employers (or some volunteers), thus making the publishing process extremely slow: everytime an extension is submitted, whether the very first or a new version, it goes to the end of the reviewing queue. Do your tables support editable grids, where I can check multiple records for example and perform some action when pressing a button Your videos on youtube are. I have a unique situation where I have a complex pdf report with static fields/columns and a grid report with dynamic columns / rows. Review, signing, and distributing policies are different at Firefox's "webstore" (AMO).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |