Allow us to disable all the input widgets inside a form from a single form variable.
↧
[Ideas] Form disabling
↧
[Ideas] [2FA/TFA] Two factor authentication for Service Center and LifeTime
Considering the fact that the cloud version does not support internal network for IP white listing, I think adding an extra layer of security to secure service center with Two factor authentication should be a standard in the Outsystems platform.
↧
↧
[Ideas] Prompt user on deployment when creating new Site property or Integration
The platform should prompt us when deploying new Site properties or REST/SOAP Integrations in a module like when we deploy a XIF with new Logical Databases or a new module on a multi-catalog environment. In most times we develop with 3rd party integrations we use with staging URLs. When deploying for the first time, the platform should prompt the user to change/confirm the values for URLs and Basic Auth credentials of those new integrations, so when the module is deployed from an environment to another errors doesn't occurr because of wrong parameters.
↧
[Ideas] Forge Improvements and Cleanup
As research for a project that I hope to get I’ve spent a large amount of time looking at components in Forge. In my opinion, a lot of work needs to be done to make this area much more useful. Much of the work is just manual effort though some coding changes would improve things as well. Below is a list of what I think Forge needs. (Note that there are some minor overlaps with existing ideas.)
I would be happy to donate time to clean up the things that can be done manually, manage the demo area and write code if given the authority to do so.
Grouping – while tagging is ok, it’s pretty inconsistent. It would be better if the ‘keeper of the forge’ designated groups (charts, reporting, connectors, etc.) and assigned components to those groups while keeping the tags. Components can be members of multiple groups. For example, a search in the forge for ‘google’ forces a tag search which only returns one component, which is incorrect. The grouping would also be used to populate the ‘similar components’ area.
Archive – Components that are no longer compatible with recent versions but kept for historical purposes (archive could be just another group). For instance, I would archive anything before 5.0 and anything dependent on enterprise manager. (Note there are a few that should just be deleted completely, particularly when newer better components exist.)
Missing data – the information supplied with each component cannot be optional as it is today. Version, stack, database, etc. need to be supplied to make the search capability useful. Full descriptions of the component's capabilities need to be supplied. For example, the Aids for Elders component has no description at all. It wastes a lot of time for a lot of people to download the component to determine what it is.
Always goes back to page one – whenever you click on a link for a component and hit the back button, the page shown is always the first page of components. It ignores your Order By selection and the page that you were on. This gets very annoying over time.
Demos and screen shots – most of the demo links don’t work and most of the components don’t even have meaningful screen shots which would take just a minute to do. (For example, the one in Dropbox that just shows a login screen is not what should be used.) For the demos, create a forge.outsystemscloud.com environment and put all the demos there.
Search - add a date range to the search that users can set (default to three years ago to today) which would allow users to skip reading old posts that don't apply to the newer version that most people are using. (Added Mar 7, 2014)
Comments?
I would be happy to donate time to clean up the things that can be done manually, manage the demo area and write code if given the authority to do so.
Grouping – while tagging is ok, it’s pretty inconsistent. It would be better if the ‘keeper of the forge’ designated groups (charts, reporting, connectors, etc.) and assigned components to those groups while keeping the tags. Components can be members of multiple groups. For example, a search in the forge for ‘google’ forces a tag search which only returns one component, which is incorrect. The grouping would also be used to populate the ‘similar components’ area.
Archive – Components that are no longer compatible with recent versions but kept for historical purposes (archive could be just another group). For instance, I would archive anything before 5.0 and anything dependent on enterprise manager. (Note there are a few that should just be deleted completely, particularly when newer better components exist.)
Missing data – the information supplied with each component cannot be optional as it is today. Version, stack, database, etc. need to be supplied to make the search capability useful. Full descriptions of the component's capabilities need to be supplied. For example, the Aids for Elders component has no description at all. It wastes a lot of time for a lot of people to download the component to determine what it is.
Always goes back to page one – whenever you click on a link for a component and hit the back button, the page shown is always the first page of components. It ignores your Order By selection and the page that you were on. This gets very annoying over time.
Demos and screen shots – most of the demo links don’t work and most of the components don’t even have meaningful screen shots which would take just a minute to do. (For example, the one in Dropbox that just shows a login screen is not what should be used.) For the demos, create a forge.outsystemscloud.com environment and put all the demos there.
Search - add a date range to the search that users can set (default to three years ago to today) which would allow users to skip reading old posts that don't apply to the newer version that most people are using. (Added Mar 7, 2014)
Comments?
↧
[Ideas] [Service Studio] Background color for variable/value field in assign
Sometimes when you'll need to assing a lot of values you can't see (quickly) what are all the variable/value fields in the assign. If you have selected one field the background color is light blue but it would be nice to have a background color (light grey for example) on every variable or value field, so you can see directy which are the variables and which values in the assign record.
I've attached a (very terrible adjusted) screenshot of an assign where I've set a grey bar to the value line's, hoping it will me a litte bit more clear what I want :).
↧
↧
[Ideas] Properties Pane: change properties for selected widgets
I'd like the posibility to select multiple widgets and then in the properties pane the properties that are not unique to a widget can be edited. For example, when selecting multiple radiobuttons I want to set the destination and style once for all radiobuttons.
↧
[Ideas] Build IPP into ServerCenter!
Please build the IPP feature into ServiceCenter,.....where the user can add a number of trust servers environment along with their associated activation code/details etc then the user can associate applications with these trusted server environments, this way an application can only be deployed to the correct server environment at all times.
An administrator can set this up and authorise the trust server environments, and will be able to control IPP of any application deployed to the AP.
↧
[Ideas] When creating a new widget the mandatory input box is highlighted automatically
Everytime we create a new widget or a run server action the mandatory input is highlighted automatically, allowing us to start writing whatever we want right after.
If there is more than one input it would highlight the first one for example.
↧
[Ideas] Extra date/time functionality when using timers
I am trying to build a task scheduler that will use OS timers to produce reports or emails, and run queries only during user-defined time windows, via the criteria shown in the attachment.
In order, the first input field shown requires a numeric value, the drop down next to it offers a choice of "minutes", "hours", "days", "weeks" and months".
The Day Range drop down offers "daily", "Mon-Fri" or "specified day".
In the attached example, it is expected that the report should run every two hours, but only between the times of 0800 and 1600hrs, Mondays to Fridays, beginning on 12 April 2019.
However there is no functionality to cater for specified days or times in this way.
The "add" functions aren't flexible enough to achieve this, and the NewDate, BuildDate and DayOfWeek functions use integers; achieving the conversion by using DateToText and TextToInteger (and then back again when required) is not ideal at runtime.
Additional functionality to cater for working week requirements and specified time/day windows would improve the function suite.
↧
↧
[Ideas] Link on Service Center Error Log Page to Open Service Studio
As exists on ECT, it will be useful to have a link on service center error page to open service studio on the query/ assign/action that origin the error.
↧
[Ideas] Add a Name propriety to the DataRefresh
The DataRefresh widget do not accept to change it name.
In order to maintain consistence with other widgets it could be nice if exist one propriety to set its name. Nowadays the default name becomes very often very big.
↧
[Ideas] Site properties shared between multiple eSpaces
It would be useful to have, what we could call, site properties that would be shared between multiple eSpaces. This would avoid the replication of site properties with the same value over multiple eSpaces.
↧
[Ideas] Show created by date and time info just like last modified by
Please show the created by date and time info just like last modified by on all elements where this information is shown.
Example on an enitity:
↧
↧
[Ideas] List_BulkSelect widget that allow diferent levels of selection (as gmail does)
Hi all,
the actual List_BulkSelect widget only allows the user to select all rows in the current table page.
I think it would be nice to allow all rows selection or all rows in the current page selection, depending of the user want to do.
An example of what I’m saying, was given by Paulo Tavares in our forum, and it is the mails selection used by Gmail…
![]()
It’s an idea.
Kind regards,
Filipe Feijão
the actual List_BulkSelect widget only allows the user to select all rows in the current table page.
I think it would be nice to allow all rows selection or all rows in the current page selection, depending of the user want to do.
An example of what I’m saying, was given by Paulo Tavares in our forum, and it is the mails selection used by Gmail…
It’s an idea.
Kind regards,
Filipe Feijão
↧
[Ideas] Simple Query: Control output entities\structures
In my opinion Simple Query lacks the opion to choose if each entity/structure is part of the ouput or not. Something like the Advance Query.
It could be a simple flag property on each entity, where we would say if that entity will or not be part of the ouput or if it just used to join the tables.
Sometimes we need to make a query, joining multiple tables, but we just want to output one of the entities. This would save the need to create custom structures or "mixed" record lists.
It could be a simple flag property on each entity, where we would say if that entity will or not be part of the ouput or if it just used to join the tables.
Sometimes we need to make a query, joining multiple tables, but we just want to output one of the entities. This would save the need to create custom structures or "mixed" record lists.
↧
[Ideas] Review the default ajax wait default positioning
It's overlapping with Chrome's URL highlighter on the bottom left corner
↧
[Ideas] Add tests to the courses.
It would be great to have a test at the end of each "path" to verify if you miss something important. Also it would be great if that question will be at the same format as on the certifications exams.
↧
↧
[Ideas] App Documentation Rating in the Forge
Can an additional rating 5 star rating measure be incorporated into the Forge for the quality of the app documentation?
The forge has many many many great apps, but I find I often spend a lot of time figuring out how to use them because the documentation is extremely lacking.
A number of the apps load with samples, but even then not all of the properties are used or documented clearly or documented at all. The forum is handy for asking questions, but now I am interrupting others.
↧
[Ideas] Add NullTextIdentifier() as an option when setting Text type parameter values on actions
This should work as the parameter setting for integer type parameter infers the type and displays NullIdentifier().
↧
[Ideas] User_Login needs to log more information around failures
It makes sense that the exception coming from User_Login is generic, to avoid giving an attacker useful information. But it is frustrating to debug anything because the messages logged are not detailed enough. User_Login needs to have more detailed logging when a login fails, so we can understand why the login is not working.
J.Ja
↧