What I would like to see in a future update/release is in NodeWorx > Packages when I look at a specific SiteWorx Account and click on Edit, I would like to see the “Package Template” indicator remain on the package that is selected.
If you have several different packages, or if a staff member where to look at that page there is really no immediate way of knowing for sure what package that SiteWorx account has be given. Even if your VERY familiar with the packages you have to review the Package features for a minute to figure it out.
So that seems like a simple fix, that would provide a very nice time savings feature.
I like this idea, but here are two (probably not insurmountable) hurdles off the top of my head:
What happens if you change one feature such as e-mail boxes so that it’s different from the base package (say the package default is 10 and you change it to 25 for 1 siteworx account)? What if you manually change all the numbers? It’s clearly not representative of the package then.
Say it only pre-selects the package name if the current options match 100% to an existing package - ok, which package is chosen if there are two or more such packages (with identical features but different names).
OK, I have though about this a lot and notice how I use this area when changes are made to a preset package.
[quote=IWorx-Paul;14917]I like this idea, but here are two (probably not insurmountable) hurdles off the top of my head:
What happens if you change one feature such as e-mail boxes so that it’s different from the base package (say the package default is 10 and you change it to 25 for 1 siteworx account)? What if you manually change all the numbers? It’s clearly not representative of the package then.[/quote]
There are two things I would like to know, 1) The original package 2) Where the changes have been made.
Any time that a change is made to…say email accounts if the original was preset as 10 (in a package only) have a cross check of the package and if it differs make the change area a color, like Red or Yellow. That way I will know that was changed from the original.
[quote=IWorx-Paul;14917] 2) Say it only pre-selects the package name if the current options match 100% to an existing package - ok, which package is chosen if there are two or more such packages (with identical features but different names).
Paul[/quote]
Here I am not sure what your getting at. Well I do, but in my thinking dont see it as a issue, at least with my limited mind,
The “logic” I believe that should be here is once the package is selected the package “NAME” is hard coded into the page, meaning, the package name reflects the name of the original package selected. It will not change until you actually change the package. And IF the package is changed the defaults will show up for each service for that associated package.
If you make service changes with a Siteworx Account like changing email accounts for an example, that will have no effect on any package template. The color change will only effect the Siteworx account that the change was applied to since the default package type was altered. I have added the graphic as an example of what I mean:
[quote=IWorx-Paul;14917] 2) Say it only pre-selects the package name if the current options match 100% to an existing package - ok, which package is chosen if there are two or more such packages (with identical features but different names).
Paul[/quote]
And I say the cross check should come from the fact, 1) The Current Package is displayed, make that a data field of some sort to allow the cross check.
And I will take it a set further if the Package is no longer avaiable, as been deleted for some reason, then nothing will happen or some warning like Package Template Deleted, no longer avaiable.
