Cached textmodules in smartforms - abap

I'm using textmodules for our footer in smartforms. If I change something in those modules and transport it, the change won't take effect on the form.
If I open the text via transaction Smartforms everything is correct.
Is there any cache I need to clean up?

You should re-generate form to get it updated

Related

Uploading files to server via JSF 2.2 and h:inputFile

UPDATE:
It turns out that there was an ajax call inside the inputFile that would cause the upload to start prematurely. That ajax was supposed to handle the selected file before the actual submit button was clicked, but neither I nor the person who coded it before me knew it would behave that way. And, as we only tested it either locally or with small files, we never noticed the problem.
I'm a newbie when it comes to file upload and I need some guidance on that subject.
I have a code that gets a file through h:inputFile then, when the submit button is pressed, sends it to the server using InputStream and OutputStream in a pretty standard way. It works well, but I'm facing a problem:
When I select the file, it takes its time to upload to the page(?). Then, when I click the submit button, it takes its time again to send that file to the server.
To make myself clear, here's a real case: I clicked the inputFile button and selected a 50mb file. It took 10min to conclude that. Then, I clicked the submit button and it took another 10min to send it to the server. That's a total 20min to upload that file, when it should have been only 10min.
Saving that time is crucial for my users, since their internet is very slow (< 1mbps) and they will be uploading videos around 40-90mb, which will take hours.
So, how do I optimize that? And, as I'm already asking, how exactly does h:inputFile work - I mean, it sets the Part in the bean, which can then be handled, but does it actually upload the file right away?
I'm using JSF 2.2.7 and GlassFish 4.
(Sorry that I didn't post the code, but I don't really think it's necessary. If that's not the case, just let me know.)

Undo functionality in Dojo

I'm using an enhanced grid in Dojo and I would like to implement "Undo" functionality .
For example after editing a cell, adding/deleting a row the user should be able to revert that action.
Any pointers how to get started?
Thanks!
Well maybe you could get inspiration from this Comand History pattern : https://gist.github.com/c210c0344ca4d4bdfacb
About the actions on DataGrid I assume you know what to do and you were just asking about some "undo mechanism" :)
I hope this will help. I've been using it for a while and it works well
Fetch and save the grid store in some variable before editing . Upon clicking the undo button/link set the grid store with the saved old store.

Receiving a form from a php page

I have a scenario that I am stuck with for a day now. There is this PHP website that I am trying to extract some data from. So I go to the website and there is this form that I can fill and when I click "submit" it takes me to another page where it has a table with all the information that I want.
I took that link and tried to parse the HTML but there was no table. And I checked that link from another computer and it was not loading up the table.
So I'm not sure what I should do here in order to get to that table? Do I have to do some sort of http request of some sort? If so How can it be done in vb.net ?
cheers
It sounds like you're having some basic difficulty with this. Depending on your browser try right clicking the 'table' page and 'View Source'. Save the HTML to a local file and open it using Visual Studio, Notepad++, or any other HTML editor.
Whta looks like a table when displayed in the browser may be encoded as a table, a div, or even a list with some clever formatting. Parsing each of those is a diferent task. without seeing the page I think that nobody will be able to help you much further.

sharepoint designer saves the changes but it does not affect

I add a tag to my page source in share point designer to use in my javascript,
and then save it. but when I refresh my page, it shows me that its not saved.
Have you checked that version control isn't acting on that resource? You should check in a major version to publish it.
Right click on the page and then there is an option to check in a major version (see below screenshots).

Programmatically save causes document to think other app changes doc when re-opening file

This is pretty weird and I would very much appreciate all help =)
I have a document based app where it should be possible to perform some actions on the document file. To do so I'm saving the document every time the document actions are called. To do so I'm using the method:
saveDocumentWithDelegate:didSaveSelector:contextInfo:
The problem is, that when closing the document, reopening it from the recent files menu and then performing the action again I'm being presented with the dialog box saying that
This document’s file has been changed by another application since you opened or saved it.
However this is not the case when using the save menu item.
I've tried with different save methods:
saveToURL:ofType:forSaveOperation:error:
And even though this results in the behavior I'm looking for there is a side effect: The save menu item becomes deactivated after performing the action.
So my question is: How should I correctly perform save operations programmatically? I've looked through the docs but I haven't seen anything which looks like an obvious solution.
All help is appreciated. Thanks
I found solution for this problem in my case.
Problem was in options in overriding of configurePersistentStoreCoordinatorForURL:ofType:modelConfiguration:storeOptions:error: method of NSPersistentDocument. Problem was solved when I delete string
[options setObject:[NSNumber numberWithBool:YES] forKey:NSSQLiteManualVacuumOption]
I used vacuum option for some reason. Don't know how but it caused problem with saving. When I refused this option the problem has disappeared.
To get it to work as you want, you can probably fix it by using the saveToURL:... method and then call -[NSWindow setDocumentEdited:] or -[NSDocument updateChangeCount:] which will stop the menu item from being disabled.
However, I'm not sure your overall approach is right. If you have a save menu item, I don't think you should be saving automatically unless you're using Lion’s auto-save feature (recommended) in which case you would call different methods.
And even if you did decide to stick with the auto-saving as you have it now, why wouldn’t you want the menu item to be disabled? It’s disabled because there are no changes to save.
Why are you auto-saving the file anyway?