I have a new table and IDO on which I am developing a form in infor syteline 8.3. Many of the fields are showing as mandatory even though they are not. Data Source\Required show False. What do I need to do to remove the mandatory indicator?
Thanks,
Grant
Please make sure the table columns should not have any not null constraint and uncheck the Required fields in the IDO Properties.
Related
I am building a zapier app using the cli.
I have an action, which has a form, with one of it's elements being a drop down, which has a hidden trigger as it's datasource.
With the context of a zap, is it possible to set the selection of the drop down, based on a value from a previous step?
David here, from the Zapier Platform team.
You can set a default value for a field, but unfortunately you can't set the value dynamically. The main reason for that is there's a good chance that the trigger your action is paired with won't be one from your app. There could be any any data of any shape coming in, so there's really no way to act directly on it.
Let me know if you've got any other questions!
edit: Even with a dropdown, there's a option to "use a custom value". That's what the users would use if they want to map a value in (or paste it themselves) rather than use the dropdown
I'm configuring our JIRA in that I want to make a new field configuration to configure a new project.
I'm currently going through a lot of fields, and would like to know the following:
If I remove a field from a screen in the FieldConfiguration, does that affect only my field configuration, or everyone in JIRA using that screen?
I'm sorry if I cannot describe it clearer, but basically I want to know if I break anything by removing the screen links in my Field Configuration.
Reason: I have fields assigned to 20 screens and dont want to keep scrolling through this the whole time.
I assume you mean hiding a field from FieldConfiguration. Since removing fields is done in the Custom Fields section.
When you hide a field it affects only your specific Field Configuration (note than more than one Issue Type from multiple projects can associate with a Field Configuration, this is probably not your case, since your are testing a new Field Configuration. But just keep that in mind).
The action that "Hide" is doing is like "forcefully" removing that field from all screens associated with tickets which use that Field Configuration.
More data: JIRA Documentation
I am developing an iOS app in which I need a UIControl that allows the user to select between 2 options and 2 options only.
For example, assume I am displaying a form in my app in which the user fills up his personal information like Name, gender, hobbies etc. Here, gender is a possible field for which there are only 2 options (other options are possible, but let's say we don't want it in our app).
I thought it will be nice to use a customized version of the UISwitch for such a case.
But then, I am beginning to think that the UISwitch is applicable only in the context where something is enabled or disabled. Can it also be used in the context where user selects one of 2 choices? Does this go against Apple's design guidelines? If yes, then what other UIControl could I use for this? (I want to use something other than a plain dropdown)
UISegmentedControl is your choice.
You can feel free to use other controls (with customized look & feel) in your app, as long as it does not confuse users.
I'd suggest a UISegmentedControl, which has the behavior you require.
I have a rails app which is already running with some users, users that I cannot delete.
Now I have added a couple of columns to the user table(like last name, nickname).
The problem is that although new sign ups can change there profile information the existing ones cannot change them.
Any help?
So, users are not able to update any of their information? Or the fields are not showing up?
If the fields are not showing up, go to:
app/views/users/edit.html.erb
And look where the form is coming from, you will most likely need to add the fields there or in
app/views/users/_form.html.erb
Now, if the users cannot edit there information, you either need to create the mechanism to do so (users#edit and users#update) or update the records yourself in the migration. If you can't do either of those things, it's a design flaw :)
I did a stupid mistake because of which it was not updating the entries in the profile.
I added new columns few of which were mandatory at the time of signup but were not mandatory when updating the profile (eg:- Date of Birth) as we thought no one would like to change their date of birth :)
So when the existing user were trying to update their profile the date of birth field was getting failed at the backend because of the validation which we had applied.
Figured it out by checking the console.
I have several Text Field items in the Root.plist of my Settings.bundle. I need all of them for my app, but I want one of them to be either hidden or un-editable by the user. E.g. When the user goes on his iPhone to Settings-->MyApp, I want one of the fields to not be visible there, or disabled for editing. Is this possible?
Sure you can. Just change the item type to title.
You still can save and read it's value from code. but, it will not appear in the app. settings.
After further research I have found the answer to my question, and the answer to the problem I am trying to solve.
Question: Can you hide/disable fields in Settings.bundle/Root.plist?
Answer: No.
Problem: How do I securely store authentication information for my app?
Answer: Built in Keychain services.
Source: Keychain Services Tasks for iOS
Short answer, you can't. Long answer: I presume you are using the Root.plist somewhere else inside your app, is that right? If so, what I'd recommend in this case, if you really need it to work the way you described, is to create two plist files, and merge them at runtime.
In other words, create Root.plist with only the fields you want the user to change in the iOS settings page (e.g, without the field you are currently trying to hide), and another .plist file with the rest of the fields you want to handle inside your app.
Then, at runtime, you first load Root.plist, and then merge the contents of the another .plist file in the data structure you'll be using.
Not very slick, but could possible work.
Setting the type in the plist from "Text Field" to "Title" works in that you get a field that is no longer editable by the user but can be read by the app.
It doesn't look quite right in as far as UI consistency goes, so this may not be the ideal solution to disable a preferences item.