When requesting a leave in Fiori the pop up shows the away time in hours instead of days:
Is there a possiblity that instead of for example 15,00 hours the pop-up shows 2 days?
Beware that many stuff in Fiori applications can also be customized by customizing your default SAP application. If your default in leave request is in hours, then that is what this Fiori app will show. Change it to days and that will be what Fiori will show.
In case you have a specific requirement to make this deviate solely in the app, then indeed you need either an extension point or create a custom implementation.
Here some additional links:
Preffered method
Old-fashioned
From what it looks like, you are asking to change a standard, delivered app?
If so, it is only possible to change it, if an Extension Point is provided at the desired place and then adapt the extended code. Check the documentation for App Extensibility: My Leave Requests.
In any case, if you haven't gone through the documentation for the app itself, with the possible customizations, check the My Leave Requests Fiori app documentation
Related
I am looking to create a timer on a quiz that I am creating in Google Forms. I have found this post here - How to add a timer to Google Forms for a School Quiz? - from 2013 where it's mentioned that scripting might make this possible eventually. I am wondering if anyone has figured this out or has a solution. Ideally I would like to have the timer start when someone opens the form and auto submit or stop receiving submissions after a set elapsed time.
Thanks in advance :)
A Previous Question has mentioned this before. Right now you are correct, you cannot time a quiz using a script at the moment. Though this question does mention some "workarounds" such as using the Form Limiter tool posted in that question.
Also this was mentioned as a viable solution:
One way is to use Qualtrics. It has a "timing" question which can
automatically submit the page once the time is complete.
So, if your sections can be placed in 3 different pages, its quite
easy: Place a timing question on the top of each section with the time
settings.
And This link Tells you how to set the general settings of time limits (such as, open test on April 14th close on April 15th). You can set specific date limits but still no timer.
For Further Reference View this Google Product Forum.
Use an addon. Some work well, others don’t. A good one is Quilgo Time and Proctoring. But as with any addon, you have to sign in. If you decide to use a different addon, be wary of the requirements. You will also have to make a Quilgo account if you use the suggested addon. But to have it stop accepting responses, you can either use an addon (Form Limit Response - Limit Form Close) or just do it in the form settings (manual turn off). Where to find manual switch for turning off responses
I started looking into OwnCloud app development to add some capabilities I would like to my server. To me it seems like Apps can't modify anything like the Login page or User Management page. Is this the case?
I want to build a user registration app and would love to integrate it into the user management page (if not and it has to exist as its own app page not a big deal). The one big problem I see so far is not being able to add a "Register" link to the login page. I could just go in and add it to the source manually, but I would like to keep the App self contained so others can use it too.
If this is not possible to do in an App I may just need to modify the core application and then see if they will accept my feature addition in a pull request.
Thanks to anyone who can shed some light on this for me. I don't want to waste my time trying to figure out how to do it with an App on the platform if it wont be doable.
After a lot of digging around I did figure out a way to do this.
In the App's app.php file, you can force a script to be loaded if the plugin is enabled:
$api->addScript('script_name'); // without .js
In that script jQuery can be used to add the elements to the page where you need them.
This was a good solution for me since I only needed to add a single button to the login page. I can see this being a bad idea if you want to make vast modifications. At that point you might as well just create a separate page that you have full control over.
Sorry for this basic question but all attempts at Googling and using facebook help only provide out of date information.
I am attempting to make my first fb app. Just an html page saying hello. From what I understand the app (or webpage) is stored on my server and I set up a facebook app that basically points to the URL of the app (or webpage) on my server.
Is this basically correct.
Where do I enter this URL information in my edit app screen. I have followed the latest fb instructions and all I see when I view the app is the admin page in fb for the app.
Does it take a long time for the page to appear.
Is there a current idiots guide. The app design is not a problem for me loading it in to facebook is the problem.
Unfortunately this wasn't very helpful, not because of what you posted but due to the fact that it appears that Facebook has updated the way in which pages are linked to again.
The pages you suggested I look at were well laid out with lots of information on them but they are already out of date and do not seem to correspond with the layout of the Facebook 'dev app' and even the fields in the form seem to have been either dropped added to renamed.
Thanks for trying to help me and I hope that FB may produce some up to date information soon and not keep changing the interface.
I can completely understand your confusion - the Facebook docs give very little information for the complete beginner. The 'Getting Started' section makes some massive assumptions and completely ignores huge key areas you need to know to get your first application up and running.
So to address your points:
Yes, this is basically correct. Apps on Facebook are served up to the user in one of two ways. Either as a 'Canvas App' or a 'Tab App'. A Tab App is an application you can install as a tab on a profile page. A Canvas App can operate on it's own page and has more room as there's no left menu as you would have on a profile page. You can configure a single app to work in both ways.
To edit your application settings, go to your own Facebook home page. Use the search bar to search for the 'Developer App'. Typing in 'developer' should do it - it should be the first result in the App section with around 830,000 monthly users. This Developer app is the window into your own app settings. You need to install it if you haven't already. It's a hub where all the apps you create will be available for you to edit. Whenever you want to edit one of your app settings in future, you click the Developer bookmark that will now be in the left menu on your own Facebook home page.
No. Apps are basically an iframe onto your code. There should be very little if any wait at all. Start with something very simple like spitting out some straight html so you can easily tell if things are set up correctly.
Yes. I found thinkdiff.net to be massively useful in the early days to get my head round the basics and then more advanced concepts. There's tons of examples ranging from very simple to quite advanced. I've just had a quick look around and found this page which should give you a decent head start in getting things moving. Note: I have no affiliation with thinkdiff.net at all - I just found them helpful in the past.
Finally, a request from me; this whole stack overflow thing is new for Facebook developers and very few people are voting up answers they consider helpful. This means new users to SO but experienced FB developers can't vote up good answers and vote down bad ones as we need enough Reputation Points to do so. If this has helped you, please ensure you vote up the answer. Of course if it was rubbish and you're just as lost, dont :D
Hope I've helped in some small way; I know I was completely lost for the first few weeks with FB development and even now there are things that make me tear my hair out! In the end it's very rewarding, but you have to put in the time. Good luck :)
I want to allow the user to enter a valid date using the iPhone’s settings application.
I have experimented with many of the PreferenceSpecifiers data node types including date.
I have two issues:
When I specify date as the type, my app within the settings app crashes. Working examples would be greatly appreciated.
Since this approach hasn’t worked for me yet, will I programmatically be able to validate the date that the user enters?
The answer to number 2 is no. The only time you can validate the data entered is the next time your app is launched. None of your app's code is run via the Settings app.
You might consider pulling this setting into your app.
Have you read this guide and this section of the App guide? They describe in detail how the settings like this work.
You won't be able to validate anything a user sets through the Settings application. Also, I don't see Date as a valid setting type anywhere, so I don't even think this is possible through the Settings application.
I would simply create a settings view within the application. That way you can control your custom logic as you see fit.
We we wondering what are some ways developers have added a help function to their apps. What are some techniques people have used?
One way we were thinking of is to us UIWebView to display a HTML file with help instructions.
Thoughts appreciated.
I'm using UIWebView right now which pretty much contains all the help in a single page, along with some JQuery things to display popups, etc. But I like the way iCab Mobile (et al.) are doing things which is a sectioned UITableView with each row a separate topic or section within their overall help information (complete with icons...) then in their bundle they have each section in its own html file, organized by localization.
Another thing in my queue for the next release is to provide a dynamic "News" view. The rough idea is as follows... I have on my server a file or CGI where I can place small bits of news I'd like to push out to users. On startup, my app checks for network availability and if present, start a thread to see if anything has changed on the server since last updating the News data. If changes present, post an alert letting user know, and asking if they'd like to read it now. At that point, the latest news is already downloaded and cached, so they can simply read it later if they want, and I won't post anymore alerts until the server file changes again. (And one could add a preference/setting to disable these alerts.)
I'm thinking this would be a good way to let people know that some nasty bug is known and fixed and an update is sitting in the queue, solicit beta testers, promote upcoming features or other apps, etc. I can see where constant alerts everytime I've got something new to promote would get annoying, so having a setting to disable them means the user never has to read them unless they want to. Although some kind of override to warn of recently discovered/fixed bugs seems sensible.
FWIW, the author of Mover+/Mover has just started doing a similar thing, though I think Emanuele is perhaps only showing one Notelet at a time, whereas I envision a bit more of a history (shown in UIWebView) until I decide to age stuff off the bottom of the stack.
I'm using a scroll/page view to show several images containing small notes. Each image then tells the user about the more advanced functions on a specific part of the app.
In my opinion the help should only contain information that isn't a 100% relevant for the use of the application. It should be things the advanced user should use to make more use of the app. It should contain gold for the power users. The "basics" should be so obvious that no help would ever be needed. If that's not the case, I think, you've failed as a developer on the iPhone platform.
(Here's a screen shot from my demo app)
I'm currently creating a fairly complicated app. I'm thinking of doing help as a semi-transparent overlay - help in text form is hard to swallow for users; it's much more helpful to just point at stuff and say "this does that".