Recently active topics

While using the Enhanced Scheduler for production planning, we've identified two improvements that would significantly increase usability and planning efficiency. 1. Move multiple activities/orders at onceCurrently, activities can only be moved individually. In real-life planning scenarios, it is often necessary to shift an entire group of activities or orders together due to schedule changes, machine downtime, or capacity adjustments.Suggested functionality:Select multiple activities using Ctrl/Shift or a selection box. Drag and drop all selected activities together. 2. Auto-scroll when dragging beyond the visible time rangeWhen moving an activity to a date outside the currently visible time range, dragging stops at the edge of the scheduler.Suggested functionality:Automatically scroll the timeline when the cursor reaches the left or right edge during a drag operation. Allow users to continue dragging activities to dates that are not currently visible without manually navigating first

When you have assigned rights to a column that has a lookup and later you change the lookup display column, the column becomes unavailable and effectively has no rights anymore. I made a validation to detect columns with lookups that have rights but are unavailable, please add this to the validation basemodel.--Lookup has rights, but is not availableselect rco.* from role_tab rt join role_col_overview rco on rco.model_id = rt.model_id and rco.branch_id = rt.branch_id and rco.role_id = rt.role_id and rco.tab_id = rt.tab_id where rt.model_id = @model_id and rt.branch_id = @branch_id and rt.select_granted = 1 -- own table has rights and rco.col_access_type in (0, 1) --0=edit, 1=read only, 3=hidden and rco.available = 0 and rco.look_up_source_tab_id is not null and rco.sf_type_of_col <> 3 -- meta hidden fieldWhat also could be considered is to automatically assign rights when changing a lookup display column that previously had rights.

We would like to use MCP on TCP to:-Add tickets and ticket-comments.-Retrieve open tickets.-Download Thinkwise products.

Current behaviorWhen multiple instances of the same screen are open in the Software Factory, they work independently. Search code is the only exception, because its instances share state:Open Search code and search for term X. Open a second Search code screen and search for term Y. Return to the first screen and click Search again.The first screen now shows the results for Y, and its search term has changed to Y.Why this is a problemUsers learn from the rest of the platform that each screen instance keeps its own context. Search code breaks that expectation without any visual indication. A user who opens a second Search code screen to compare results, or to keep an earlier search at hand, silently loses the first one and may act on results they did not ask for. Even if this is intended, from a user's perspective it is indistinguishable from a defect.ProposalMake behavior consistent (orthogonal) across the platform:Preferred: each Search code instance keeps its own state (search term, f

Code search is a great tool, but it gives too much results. For debugging a problem in a live application a lot of the results are irrelevant. Most time i only want to see task templates, triggers and procedure templates. To find which task/trigger etc affects a certain table. My suggestion would be:add a checkbox: exclude non-assigned templates (active by default)add a checkbox: exclude gui templates (this only shows code that would impact results, so only templates for tasks, procedures, subroutines, triggers (i might forget one here?) 

We like to have more control over field widths, because often you wish to give fields a absolute widthExamples:house number postal code dates bank accounts etc..When fields are on the same line it can have a mix of fixed and flexible widths.It should be more easy to set this up in the Software Factory.         

Our users need to search for multiple articles or other options in their work, to change statusses of those, or edit other data combined with the selection, therefor they paste a total selection with multiple search terms seperated by a character.They want to search / filter like this: 2508*|2517*|etc… - it can also be with a comma to seperate the keywords, or other regex variants.But now they need to filter for them one by one by one. Which takes a really long time.Can we add the possibility to search or filter on multiple option by filling in the options in one long query or string?

Currently printing files is only possible from Windows. To increase platform indepedence I would like to see file printing implemented on Linux as well.Follow-up for: 

Upon opening a new Document in the Universal GUI the first value in the top left (at least for Western writing) Screen Component should be activated. This especially goes for the Grid component, where it seems as if the first Row is selected. In below example it took me 44 tabs to get to the first column value of the seemingly selected Row. Could the Universal GUI be a bit smarter here? 

When we do our upgrades (every 3 weeks) of our applications we take the application offline (deactivate in IAM) right before we execute the source code on the database and we put it back online after the IAM sync.However as time goes on our model grows and the IAM sync action in SF is taking up to 8min right now, the majority of that time goes into generating the sync code. If we could generate the sync code separately from the actual sync this would decrease the required downtime for upgrades by a big percentage because you could generate the sync code before taking the application offline. On top of that it is pretty easy to forget to do an IAM sync, it would be nice to have it part of the creation process/screen. 

Can you change something on the visibility of the inactive TABS. In the WIN GUI the colored Icons were made grey on an inactive tab. When the tab was active the colored icon was shown. So it was very clear for users when the tab was inactive. And with using color it was also very clear when the tab was active.In the current Universal version the inactive tab is shown with very lightly reduced colors. As wel the text of the tab as the icon. This is the inactive variant And this is the active variant. When you see them here in exploded format and next to each other the difference can be seen. However in the application you see one or the other, and they are much smaller. So for the user it’s much harder to see if the tab is active or not.The grey variant for the inactive variant in the WIN GUI was much and much better and much more clear to the user