Looking back to the projects we have done/made in Filemaker/Servoy we came to the conclusion, how much work/hazzle we have to implement a standard solution for different customers. What I mean is the print-layouts for: Invoice, Orders, Letters, etc..etc.. One customer use envelopes with shine-thru venster at the left, the other at the right. One customer wants to use on other font, etc..etc. For every customer, this is a one-time-action. But here it comes: what to do with update’s??
In Filemaker we have accomplished that a user can edit certain forms, by using a plugin: SecureFM. This gives only a Super-User acces to the layout of certain forms, but also here; what to do with update’s? The user-has to all work over again, after an update.
Would’nt it be nice that there was a possibility (Developer LITE?) that you give a Super-User acces to certain (print)forms, where he can only change edit-facilities like, moving objects, color, fonts, place a (already-made)field on the layout. etc..etc.. and that this form stays in shape, when an update is performed.
HJK:
In Filemaker we have accomplished that a user can edit certain forms, by using a plugin: SecureFM. This gives only a Super-User acces to the layout of certain forms, but also here; what to do with update’s? The user-has to all work over again, after an update.
Wouldn’t a plugin (like FM) do the job so a developer (we) can decide if a costomer can alter a specific layout and/or specific objects.
The user-has to all work over again, after an update.
Not any more if the developer uses the repository or solution-file from the customer, one of the big advantages of Servoy > seperated data and structure
Not any more if the developer uses the repository or solution-file from the customer, one of the big advantages of Servoy > seperated data and structure
The problem is that you have to develop all things over again, if you use the solution of the customer. We have a standard-solution (now in Filemaker) which is used by approx. 100 customers. So this is not an option.
And a printform is part of the structure, so it will be overwritten by an update!
The easiest way indeed is a kind of plugin, where we (developer) decide which forms can be edited.
Not any more if the developer uses the repository or solution-file from the customer, one of the big advantages of Servoy > seperated data and structure
The problem is that you have to develop all things over again, if you use the solution of the customer. We have a standard-solution (now in Filemaker) which is used by approx. 100 customers. So this is not an option.
And a printform is part of the structure, so it will be overwritten by an update!
The easiest way indeed is a kind of plugin, where we (developer) decide which forms can be edited.
What you describe is already possible. If you or your customers design new forms and you bring out a new version of your solution you can merge that into one solution by checking one box at import time. Just make sure that your customer doesnt name forms the same as future new forms you define. To avoid this have the customer prefix the forms they create with a set of characters.
We are looking into limited dev-access of customers, this comes in handy if you don’t want to give them design access to your entire solution, you don’t need it for customer specific forms, that’s already possible.
Yes I know this is possible, but I dont understand it quitly,
for example we have an invoice-print-form, that is used by all the customers, and this form has the same name, because it is used in the method’s. Every customer (different locations) wants to change minor things, like the place of the adress, extra text, etc..
How do I prevent that this form is overwritten, by an update for all customers?
Can you give me some examples?
Do you understand my problem?
jaleman:
We are looking into limited dev-access of customers, this comes in handy if you don’t want to give them design access to your entire solution, you don’t need it for customer specific forms, that’s already possible.
Will this be possible in the Servoy Client, or in a other Developer?
Client would be nice
We are looking into limited dev-access of customers, this comes in handy if you don’t want to give them design access to your entire solution, you don’t need it for customer specific forms, that’s already possible.
is there any news on this one?
It is really a must have, for standard-solutions, that are used by different companies.
No news at this moment. As soon as we do have news we will post immediately, no need to post on posts.
Right now priority No.1 is to get 2.0 out of the door. After that we will inventarise based on everybodies input what will get developed first and as soon as we know we will post it.
Not any more if the developer uses the repository or solution-file from the customer, one of the big advantages of Servoy > seperated data and structure
The problem is that you have to develop all things over again, if you use the solution of the customer. We have a standard-solution (now in Filemaker) which is used by approx. 100 customers. So this is not an option.
And a printform is part of the structure, so it will be overwritten by an update!
The easiest way indeed is a kind of plugin, where we (developer) decide which forms can be edited.
One of the things I can imagine is a form becoming an object that can be created ad-hoc. In this sense a Java developer could write a simple “drawing” type of plugin. This plugin could offer the ability to specify page settings, positioning of common elements (such as return address, sender address, billing address, etc.), inclusion of certain fields and control over other items that would be printed.
You would then code the automatic drafting of the form based on the “painted” template created by the user. The instructions for the form could be saved and then it could be created and merged with data to provide the desired output.
There’s a lot of abstraction in this concept, but it’s doable if we could create ad-hoc forms as new objects. Meaning we could create forms using code.
But up to a certain level it is ofcourse already possible to give the user a template form.
I do that with 3 rtf fields (header, body and footer) where the user can input something like 30 predefined fields including an invoice and offer part.
Because it is rtf the user can change everything like font information etc.
When the user then actually uses the form I replace the fields formatted like <> with %%fieldname%% per form part and print it…
I even have the possibility to show a logo in the header (visible/invisible)…
HJK:
Would’nt it be nice that there was a possibility (Developer LITE?) that you give a Super-User acces to certain (print)forms, where he can only change edit-facilities like, moving objects, color, fonts, place a (already-made)field on the layout. etc..etc.. and that this form stays in shape, when an update is performed.
Sorry to post on a post, but I have to say this feature would go to the top of my list right now! Really glad we have this forum. Glad others have the same interest.
I’ve been researching various SQL reporting tools for my clients just for this reason - they need to be able to build reports without messing up the solution or having their work lost when I perform an update (I don’t understand how “merging a solution” would be an option as I’d have to give them full access and they could mess too much up. What if they build a report but forget to make the field non-editable and change data? Or what if they get into a layout they’re not supposed to and mess that up. This happens all the time).
I’ve really been wondering how Servoy would deliver on the idea that “companies no longer need … Crystal Reports for reporting…” It was really looking like we’d still need this.
Best of luck pushing 2.0 out the door. Looking forward to polling and discussing the next set of features on this great product.