Roel, Would be great... I think that's just what I need.... Thx.
Henk, Still my problem (or Idea) is not clear I fear.... Thing is, I got everything more or less working, using the Extender in de SF. But for one particular thing we use the scheduler as a "Month" schedule. Or actually, a schedule for the previous 2 weeks and the coming 4 weeks. Using the Extender properties minimum and maximum date is exactly what I want to do here, but I don't think it's currently possible to do dynamically. I want to set the boundaries of the schedule in my application, because the view behind it is so damn slow (because of the complexity and huge amount of data to process). Keeping the view limited to these 6 weeks is one thing, but if I can't set the boundaries of the schedulerer a user can browse further into the future or past, which results in the GUI doing another query on de database (which won't do any good as the view is limited to the mentioned 6 weeks). All in all: I want to be able to set a property of the Extender from within my code (liky
Henk, I don't get your response. I mean: the properties I'm talking about are already available in the Extender (example minimum and maximum date for the scheduler). It is possible to set those values in de Extender, but that is of no use, because it should be calculated when the user opens the scheduler. Like in a DEFAULT procedure. I don't think it is currently possible to add such code to ones project. Or am I missing something?
Anne, So a new processflow where task create_task_ref is called and the missing parameters are filled with the parameters used in task copy_task_parmtr? (I looked up the names of the procedures in the debug window) Yeah, that would help a lot I think.
Ah, indeed, I was mislead by the SF part in the Wish. But such a control in the mobile version could come in handy when measuring the borders of a terrain or when calling in a a stranded vehicle in our case for example. So I'm definately going to vote for this one...
Harm, I'm not sure what you mean by a GPS Location Control in the SF. Is the Maps extender perhaps right for you? If you don't already use it, Thinkwise can add the extender in the GUI packages for download. We use it in a few displays in our project for tracking&tracing and Geo Fencing purposes. [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/b91a2186-201b-4fc3-bda3-201f241d7778.png[/img] [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/9ed9b2da-73a4-4eee-871c-b4e55b42d6e3.png[/img]
Since using version 2018.3 a message is displayed when starting a project in developer mode, telling the user that extenders could or should be created and configured in the Software Factory. I just read this blog. so I thought: "Let's have a look at this feature". Creating an extender is simple enough, but getting an idea what could or should be entered in each of the properties ( mandatory ones or not) is up to the developers imagination or best guessing. Without an understanding of what is built in the corresponding DLL. [img]https://uploads-eu-west-1.insided.com/thinkwise-en/attachment/fd23578f-0be8-43d1-acd3-3b90d297824f.png[/img] So while this blog is an interesting one, it won't get SF developers getting started entering the appropriate and/or valid values in each property. For instance: the "Initial zoom level", a binary value.. What is what in this case? I have multiple tables using the maps extender. Do I have to create an extender for each one? Will there be a
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.