Can we prevent the user from saving the document?

Hi All,
I want to know that can we prevent the user from saving an illustrator doc till a condition match.
if we can, then how?
Please comment.
Thanks

You can't prevent it, no. You could continually set the document modified flag to false, which would prevent regular 'Save', but they could always do 'Save As' -- nothing can stop that.

Similar Messages

Can I prevent a user from Deleting the Group Policy deployed power plan?

I have Power Manager version 3.20 installed and am using the Group Policy template to deploy a customized power plan. I do not want my users to have the ability to delete this custom plan, but I cannot find the option in the Group Policy to change the setting that would grey-out the Delete button in Power Manager.
I have located the registry value that changes the function of Power Manager, it is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lenovo\PWRMGRV\PowerSchemes\42617646-BC99-48E2-B3AF-C562C25F4098\ProhibitModification. If the value is 0, then the delete button is available. If the value is 5, then the delete button is greyed-out.
The problems is that the Power Plan ID number (the 42617646-BC99... part in the reg key above) changes from computer to computer. That ID string seems to be tied somehow to the specific computer. So, I cannot just create a Group Policy Preference to change that value in the registry, because that value is always going to have a different name.
The computers are all ThinkPad T400 model and are running Windows 7 Enterprise 64-bit.
Can anyone suggest a different method to change this setting? If not, is there any chance that the Power Manager application can be upgraded to include this control?
Thank you!

welcome to the forum!
to add to what gan said, page 6 of the power manager deployment guide covers this policy over active directory.
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TVAN-ADMIN#pmat
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70419
ThinkStation C20
ThinkPad X1C · X220 · X60T · s30 · 600

How to stop the users from saving the PO when there is error message

Hi Guru,
The error message had appeared but the user still can choose to hold the PO even though there is an error.
They do not want to let the user to have a choice to save the PO once there is an error.
Please advice where i can out this checking in.

Dear Sally,
As per OSS: Note 606728 - Hold Functionality of the PR & PO - Gaps.
The only way you can stop the hold functionality is by implementing the BADI: ME_PROCESS_PO_CUST.
I am copying the OSS text for your reference.
Summary
Symptom
It is possible in the system to create/hold a purchase order (PO) referencing a held purchase requisition (PR), but your business process requires that this not be possible in your installation.
Other terms
Hold, ME21N, ME52N, Parking, Save without Check, Held PR, PO referencing a held PR, Commitments, reduction of PR by a held PO
Reason and Prerequisites
Cause: The functionality is not provided in EA-PS 110.
Prerequisites : You must be on EA-PS 110 to implement this note
Solution
You can implement some customer BAdI's provided by SAP to get this functionality. Note that customer implementations of the BAdI's provided by SAP are upwardly compatible. The text that follows gives details of how to implement the customer BAdI's to accomplish this functionality.
This functionality might be provided in future releases. However, we cannot make any binding statements at this time in regard to the scope of this development and when it will become available.
The following are the steps required to implement the customer BAdI to give an error message when a user tries to create a PO referencing a held PR.
1. Go to transaction SE18. Enter the definition name as ME_PROCESS_PO_CUST. Select the push button display.
a) Choose Implementation -> Create.
b) Enter an implementation name. Choose Enter.
c) Enter a short text to describe the purpose of the implementation, then save the implementation.
d) Select the tab interface, then double-click the method "process_item".
e) Create a message to issue a message that the PR is on hold.
f) Enter the following code in the method:
                    DATA: LS_MEPOITEM TYPE MEPOITEM.
                    DATA : MEMORY     TYPE EBAN-MEMORY.
get current data from business object
                    LS_MEPOITEM = IM_ITEM->GET_DATA( ).
Check if the PO references a PR and check if the PR is not on hold
If the PR is on hold give an error message
                      IF NOT LS_MEPOITEM-BANFN IS INITIAL.
                        SELECT SINGLE MEMORY INTO MEMORY
                        FROM EBAN WHERE BANFN = LS_MEPOITEM-BANFN
                                    AND BNFPO = LS_MEPOITEM-BNFPO.
                        IF MEMORY = 'X'.
                           MESSAGE E900(ZM). "The message that you have created in step 6
                        ENDIF.
                    ENDIF.
g) Activate the implementation.
2. If you do not want to let the user put the PO referencing a held PR on hold, you have to also implement the BAdI ME_HOLD_PO. The following are the steps to implement the BAdI.
a) Go to transaction SE18.Enter the definition name as ME_HOLD_PO and click on the 'DISPLAY' button.
b) Go to Implementation -> Create.
c) Enter an implementation name, then choose Enter.
d) Give some short text to describe the purpose of the implementation, then save the implementation.
e) Select the tab interface. Double-click the method IS_ALLOWED.
f) Enter the following code in the method:
                    DATA : IM_BEKPO_WA TYPE BEKPO.
                    DATA : MEMORY TYPE EBAN-MEMORY.
                    *-Look if the PO refers to a Held PR
                    LOOP AT IM_BEKPO INTO IM_BEKPO_WA
                           WHERE NOT BANFN IS INITIAL.
                             SELECT SINGLE MEMORY INTO MEMORY
                             FROM EBAN WHERE BANFN = IM_BEKPO_WA-BANFN
                                        AND BNFPO = IM_BEKPO_WA-BNFPO.
                             IF MEMORY = 'X'.
                    *-Do not allow the PO to be kept on hold
                    *-if the PO is refering a held PR
                               CH_ALLOWED = ' '.
                              ENDIF.
                    ENDLOOP.
g) Activate the implementation.
I hope it helps.
Kind Regards,
Prakash

How to prevent multiple users from updating the same data in coherence

Hi,
I have a Java Web Application and for data cache am using coherence 3.5. The same data maybe shared by multiple users which maybe in hundreds. Now how do I prevent multiple users from updating the same data in coherence i.e. is there something in coherence that will only allow one user a time to update. If one user is in a process of updating a data in coherence and some other user also tries to update then the second user should get an error.
Thanks

I have a question on the same line. How can I restrict someone from updating a cache value when I a process is already working on it. I tried locking the cache key but it does not stop other process to update it , it only does not allow other process to get lock on it.

Is there a way to prevent a user from using the graph cursor legend to delete a cursor?

I would like to have 2 cursors on a graph that can't be deleted by the user.

Hi Dennis,
I'm having this problem as well, and found your post. Are you referring to the Enabled State of the entire graph? If so, this prevents the user from moving the cursor at all while the VI is running, which, of course, defeats the purpose of having a cursor at all. Ideally, I would like to show the cursor palette and disable it's run-time shortcut menu. This doesn't appear to be possible. One workaround would be to hide the palle and instead include some indicators that show the cursors' values. I'd prefer to show the palette to keep the program simpler.
Any other solutions?
Thanks,
Alan
Alan Blankman, Technical Product Marketing Manager and LabVIEW Developer
LeCroy Corporation
800-553-2769 x 4412
http://www.lecroy.com
[email protected]

Prevent a user from changing the Project ID in P6 EPPM 8.3.7

Does anyone know if there is a Global or Project Security Profile privilege that will prevent a user from changing the Project ID on an existing Project? We are using Primavera P6 EPPM 8.3.7
Thank you,
Eric

Hi,
Below project security profile may help you,
Edit Project Details Except Costs/Financials
Determines whether the profile will enable users to edit fields in General, Dates, Defaults, Resources, and Settings tabs in Project Details. To assign a project baselines, users must also have the "Assign Project Baselines" project privilege assigned to their profile.
Regards,
Marcos

I have checked around the internet, but still can't find any answers. How can I prevent incoming mail from interrupting the music I am listening to on my iPhone? That 1-second muting function drives me insane, especially when a lot of mail is coming in.

I have checked around the internet, but still can't find any answers. How can I prevent incoming mail from interrupting the music I am listening to on my iPhone? That 1-second muting function drives me insane, especially when a lot of mail is coming in.

If you want to hear your music on iPhone without interruption, switch Settings > Airplane Mode: ON.

How can we prevent a user from entering a value in Parameter Field?

how can we prevent a user from entering a value in Parameter Field and Select-options Field?

make it invisible, make it inactive, make it display only.
if the field is not there or not to be seen the user WILL have problems inputting data.
BUT once the field is there you can NOT prevent that the user fills it with data.
all you can do is on PAI check if the data the user inputted was good or bad, and clear his inputs, but you can NOT prevent him inputting something.

How to secure the users from deleting the work items

Hi all,
I have a question like this.........whether we could secure the users from deleting the work items by someone in the Project and also assigning a specific user to allow them to delete the idoc.
Please help me on this as this is critical.........
Thanks in advance
Chakri

One of t he possible way is, ask the basis team to create users as Service Users and you can determine whether the login user is whether a service or dialog user by using the a bapi BAPI_USER_GET_DETAIL under the exporting parameter logondata with field USRTYP where if the logged in user is Service user then this field will be populated as S if the user is a dialog user then it will be populated as A.
Now in more efficient way of fixing this is get the list of users for whom you donot want to give the authorization of deleting workitems and assign the appropriate role for all the listed users...
for roles and authorizations i hope the basis team is the right team to consult....

I need to prevent unauthorized users from accessing the application pages

Hi^^,
I have created an application in jsp and servlets. It has several pages like manager, supervisor accountant. I need to prevent unauthorised users from accessing these pages. In other words I need to implement a filter. Anyone who types a url other than that of the login page needs to be blocked. However I am not able to conceptualize the code that is going to be inside the doFilter() method. Please help
Sincerely,
Prashant

Hi^^,
I admit that there were some mistakes in the previous posting. I have corrected the mistakes and now there is going to be no compile time error. However when i put in the login id and the password it is redirecting me to the login page. I think that the front end jsp is directing the control to the controller servlet. But as "YOU" have pointed out in your previous post,
"by default requestDispatcher.forward(...) does not pass through the filter change. If the user requests the login page from their browser however, then they will still get the error message, which may not be appropriate."
I feel we need to somehow make the code pass through the requestDispatcher.forward(...) method of the servlet.
I am again posting the corrected code.
package com;
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class SecurityFilter implements Filter
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws   ServletException, IOException
HttpServletRequest req = (HttpServletRequest)request;
HttpServletResponse res = (HttpServletResponse)response;
String X = req.getRequestURI();
if(X.equals(http://localhost:8080/MyProject/LoginPage.jsp))
     //writing code for passing through the filter
     final class MyGenericFilter implements javax.servlet.Filter
      public FilterConfig filterConfig;
      public void doFilter( final ServletRequest request, final ServletResponse response, FilterChain chain) throws java.io.IOExeption, javax.servlet.ServletException
      chain.doFilter(request,response);
      public void init(final FilterConfig filterConfig)
      this.filterConfig = filterConfig;
      public void destroy()
else
   HttpSession session = req.getSession();
   String username = (String)session.getAttribute("username");
   if(null==username)
     request.setAttribute("Error","Session has ended. Please login");
     RequestDispatcher rd = request.getRequestDispatcher("Login.jsp");
     rd.forward(request,response);
     chain.doFilter(request,response);
    else
     RequestDispatcher rd = request.getRequestDispatcher("X");
     rd.forward(request,response);
public void init(final FilterConfig filterConfig)throws ServletException
      public void destroy()
Edited by: pksingh79 on Aug 12, 2008 5:23 AM

How to Restrict the users from changing the Default variant of report.

Hello everybody,
The requirement is to restrict the users to save and overwrite the default layout variant (Layout for higher managenet)set for the report, but at the same time they should be able to change and save the other layouts for which they are having access.
I have written the logic in the program which is working fine for all the scenario when we execute the report. But the logic doesnt work if the user is selecting the layout on the output screen of the report.
for e.g if the user runs the report using the layout varaint for which he is having the authorization then he gets the all 4 options so he then he can select the layout for which he is not authorized and he can overwrite.
i have debugged and check as i have found that after the report output is shown all the layout paramater is controllled by the statndard SAP objects.
Can anyone help me out in this issue.
Thankyou in advance.
*to get the default layout variant.
w_save = 'A'.
if p_vari is initial.
    clear disvariant.
    disvariant-report = sy-repid.
    w_variant = disvariant.
    call function 'REUSE_ALV_VARIANT_DEFAULT_GET'
      exporting
        i_save     = w_save
      changing
        cs_variant = w_variant
      exceptions
        not_found = 2.
    if sy-subrc = 0.
      p_vari = w_variant-variant.
    endif.
endif.
*logic to check user authorization to change the layout setting.
if p_vari = c_layout.
    if not sy-uname is initial.
      select single * from agr_users
              where agr_name = c_role
              and   uname    = sy-uname.
      if sy-subrc = 0.
        w_save = 'A'.
      else.
        w_save = ' '.
      endif.
    endif.
endif.
Regards,
Satish.

Hi Maine,
Thanks for your reply.
As you mentioned for your own program, you can control the parameter "I_SAVE", when calling "REUSE_ALV_GRID_DISPLAY".
so already i have use the same logic and control the parameter through I_SAVE and here i am calling method ALV_GRID->SET_TABLE_FOR_FIRST_DISPLAY instead of "REUSE_ALV_GRID_DISPLAY".
and it works fine when we execute the report but the logic doesnt work when the user tries to change and save the layout variant on the output screen of the report.
Regards,
Satish

How can I stop a user from saving over "standard" workbooks in a role?

Hello -
We are using BEx Analyzer 7.0.
I need help restricting our regular users so they can only save workbooks to their favorites and cannot override workbooks published to roles by our super users / authors.
My understanding is the regular users need the following in order to save workbooks to favorites.
S_GUI Activity = 60
S_BDS_DS Activities = 03 and 30 Class Type = OT
These users are able to save to their favorites.
However, if they open a workbook from a role and then just choose Save -> Workbook, it allows them to save their changed version of the workbook over the "standard" workbook that was published to the role for all users.
What can I do to only allow them to save to their favorites and not be able to override the standard workbooks in regular roles?
Our super user / authors have the following security to allow them to publish to roles.
S_USER_AGR with Activities = 01, 02 and 06 (Create, Change and Delete)
Our regular users have
S_USER_AGR but only with activities 03 and 08 (Display and Display Changes)
Any help that can be provided would be greatly appeciated. This is very frustrating.
Thank you -
Ann

Hello Anne,
Inspite of restricting the authorisation object S_BDS_DS you are not able to restrict the users in overwriting the workbooks, please implement the note 1167094 in your system.
Implementing this note with the help of yout BASIS team would surely fix your issue.
Let me know if this helps. Thanks.
Best Regds,
Suyog Chakot...

How to stop the users from changing the Decimal in SAP

How to stop the users from changing User Profile

Hai,
It is not possible to restrict SU3 to display, because it has only S_TCODE has the authorization object.
If you really want to restrict users from changing their profile you have to remove the SU3 access and give SU1 or SU2 which gives access only to Personnel details and Parameters.
Hope this helps.
Regards,
Yoganand.V

How do I stop the user from saving information onto my original?

Hello everyone,
I created a form that I plan to put on a website but, I have one problem. The user is allowed to fill-in the form and save the new data onto the original. How can I set up the form so that the user cannot save over the original but, still be able to save a copy and use the "Submit by Email" button? Any help would be appreciated.
Thank you,

Use these steps to remove saved (form) data from a drop down list:
#Click the (empty) input field on the web page to open the drop down list
#Highlight an entry in the drop down list
#Press the Delete key (on Mac: Shift+Delete) to remove it.
*http://kb.mozillazine.org/Deleting_autocomplete_entries
You can remove saved Password(s) here:
* Tools > Options > Security: Passwords: "Saved Passwords" > "Show Passwords"
*http://kb.mozillazine.org/Password_Manager
Websites remembering you and automatically log you on is stored in a cookie.<br />
So you need to remove the cookies from that site to reset this choice.
*Tools > Options > Privacy > Cookies: "Show Cookies"

How do I disallow users from saving the data they enter into an Editable form?

Hi all,
I am working with a client who does NOT want their users to be able to save their data. In other words, when the user opens the PDF file, they can enter data into the editable fields, but they should NOT be able to save that data as part of the PDF.
Does that make sense?
My client doesn't want the user to be able to save a local copy of the PDF with any of the data entered onto the form.
Based on what I've found in my research, as of Version 11, Adobe Reader now allows users to save their data. Unfortunately, my client doesn't want that.
Any help?
Thanks,
Steve

About the best you can do is include a JavaScript that resets the form when it is saved, so no entered data remains in the fields. The problem with this approach is JavaScript can be disabled, resulting in the form not being cleared and allowing the filled-in form to be saved.
You can address this with an additional JavaScript that runs when the form is opened that sets all of the fields from read-only to not read-only, allowing the fields to be filled-in. If JavaScript is disabled, the script won't run when the document is opened and the fields will remain read-only and therefore not fillable.
The user would be able to work around this by having JavaScript enabled when the document is opened and disabling it after filling-in the form but before saving it. Most users would not be aware of how to do this though.
If there are rules/regulations/laws in place that require something more certain, you'll have to take a different approach.

Can we prevent the user from saving the document?

Similar Messages

Maybe you are looking for