Mandatory Baselines dissapearing

Dear All,
The last couple of days I've noticed some very strange things with the patch management mandatory baselines. They keep disappearing after a server reboot. I've been doing server reboots with trying to upgrade 10.3.
Originally I had assigned patches as a mandatory baseline to my Windows XP workstation dynamic group. A couple of days ago I noticed that the base line had gone. I then went to add them in again.
It looked ok for a day, so I did a reboot. No patches were listed in patch management at all.
Did a Subscription update and then they slowly began to come back. But still, annoyingly, mandatory baseline had gone against the xp workstation group. I'll have to go through the painful process of adding them in again.
Has this going something to do with removing the system updates e.g. 10.2, 10.2.1 etc from the system update as part of the 10.3 upgrade? (Still can't upgrade to 10.3a by the way, have another thread for this)
Please help anyone, this weekend has been a very bad one for ZCM (I'm not the only one).
cheers
Matt

mtaylor1979,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Similar Messages

  • Patches in a mandatory Baseline not deployed

    We are in the process of migrating from Patchlink to ZCM. I like to use mandatory baselines if at all possible. I took this project over after there was some configurations were already done. I notice that none of the patches I have added to the mandatory baseline are being pushed out to the clients. I made sure that the refresh was scheduled not set to manual. From what I am seeing the patches should automatically go out to the client. Does anyone have an idea where I can start to get this straightened out? Where can you find a book that will help with configuration?

    jkoelsch,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • Removing patches from mandatory Baseline

    Hello,
    (system: sles 11 + zcm 11.2.3a)
    what happens if you remove a patch from the mandatory baseline?
    Does removal from the baseline imply deinstallation on clients which belong to that baseline?
    thx,
    hugo

    It is my understanding that if you remove a Mandatory baseline and a workstation has already deployed that baseline the deployed patch/software stays on the system. The Baseline removal only prevents future or non-patched devices from deploying the patch or software in the future.
    Richard

  • ZCM 10.3- XP patch install force reboot - need to suppress

    We have recently upgraded all systems to ZCM 10.3 but it seems that certain XP patches are causing our PCs to reboot after installation.
    Even though I have put this thread in Patch management, I also noticed one instance of an msi bundle install causing it as well.
    So it might be MSI's in general. It's just that more often than not it's patches.
    So far this week my machine has rebooted 3 times. Some users today have had it reboot twice todays after successive patch installs.
    We really need a way to suppress reboots after any patch/bundle install because it's giving users no warning and they are losing work.

    For us, it's the WinLogon process that as initiated the restart of our
    computers.
    Why ??? We are looking for it...
    "Jim Koerner" <[email protected]> a crit dans le message de groupe de
    discussion : 2u7Vn.32390$[email protected]..
    > If anyone with this problem gets a chance, look in your system event log
    > and see if you have a similar event at the time of the reboot.
    >
    > The process C:\Windows\system32\wbem\wmiprvse.exe (JKOERNER-PC) has
    > initiated the restart of computer JKOERNER-PC on behalf of user NT
    > AUTHORITY\SYSTEM for the following reason: No title for this reason could
    > be found
    > Reason Code: 0x80070015
    > Shutdown Type: restart
    > Comment:
    >
    > Jim
    >
    > "Jim Koerner" <[email protected]> wrote in message
    > news:XAHUn.31247$[email protected] ..
    >> We have this problem too. Some XP and Windows 7 machine seem to auto
    >> reboot after patches are added to our baseline. Have not figured out
    >> what causes it. 'Enable auto reboot of mandatory baseline" is not
    >> checked in 'Mandatory Baseline Settings" so reboots should not happen
    >> with baselined patches.
    >>
    >> Jim
    >>
    >> "bkohary" <[email protected]> wrote in message
    >> news:[email protected]..
    >>>
    >>> We have recently upgraded all systems to ZCM 10.3 but it seems that
    >>> certain XP patches are causing our PCs to reboot after installation.
    >>>
    >>> Even though I have put this thread in Patch management, I also noticed
    >>> one instance of an msi bundle install causing it as well.
    >>>
    >>> So it might be MSI's in general. It's just that more often than not
    >>> it's patches.
    >>> So far this week my machine has rebooted 3 times. Some users today have
    >>> had it reboot twice todays after successive patch installs.
    >>>
    >>> We really need a way to suppress reboots after any patch/bundle install
    >>> because it's giving users no warning and they are losing work.
    >>>
    >>>
    >>> --
    >>> bkohary
    >>
    >>

  • Is running a zcm report save to disk without ZRS possible ?

    In a non-ZRS ZCM11.1a setup, is there a way to use one of the custom reports to run saving to disk on the server itself via command line ? The zcm servers are SLES11SP1 x_64.
    Thanks in advance
    Nimal

    nimals wrote:
    >
    > Reporting commands seems to work only if ZRS is installed. For
    > example, from one of our production servers that has no ZRS servers
    > in the zone we get:
    >
    > ---------------------------------
    > zenasprod02:~ # zman rpl WID -r -f "Novell ZENworks Reports"
    >
    > Username:Administrator
    > Password:********
    >
    > Error:You do not have this feature installed.
    > Error:Failed to connect to the CMS server. For more information, see
    > the zman log.
    > Error:An internal error occurred. Please see the zman log for full
    > stack trace.
    >
    >
    > ERROR: 16
    > -----------------------------------------
    >
    > But from a test machine that has ZRS the same command gives:
    >
    > ------------------------------------------
    > sles11vm1:~ # zman rpl WID -r -f "Novell ZENworks Reports"
    >
    > Username:Administrator
    > Password:*******
    >
    >
    > Report ID | Name | Type
    >
    > > Folder | Description
    > ----------+------------------------------------------------+----------
    > -----------------+-----------------------------+------------ 1200
    > | Licensed Products And Entitlements | Web Intelligence
    > Document | License Management | 1195 | Allocations vs
    > Installations | Web Intelligence Document | License
    > Allocation | 1198 | Current Allocations
    > | Web Intelligence Document | License Allocation |
    > 1194 | Demographic Over-Allocation | Web
    > Intelligence Document | License Allocation |
    > 1197 | Demographic Under-Allocation | Web
    > Intelligence Document | License Allocation |
    > 1192 | Device Over-Allocation | Web
    > Intelligence Document | License Allocation |
    > 1196 | Duplicate Allocations | Web
    > Intelligence Document | License Allocation |
    > 1199 | Installations with no Allocations | Web
    > Intelligence Document | License Allocation |
    > 1193 | Licensed Products Allocations | Web
    > Intelligence Document | License Allocation |
    > 1190 | Purchase Record Detail | Web
    > Intelligence Document | Purchases |
    > 1189 | Purchase Record Summary | Web
    > Intelligence Document | Purchases |
    > 1186 | Compliance Status | Web
    > Intelligence Document | Software Compliance |
    > 1185 | Discovered Product Summary | Web
    > Intelligence Document | Software Compliance |
    > 1187 | Software Compliance | Web
    > Intelligence Document | Software Compliance |
    > 1202 | Discovered Standalone Components | Web
    > Intelligence Document | Suites |
    > 1238 | Bundle Deployment Details | Web
    > Intelligence Document | Bundles and Policies |
    > 1235 | Bundle Deployment Details - Devices | Web
    > Intelligence Document | Bundles and Policies |
    > 1234 | Bundle Deployment Status | Web
    > Intelligence Document | Bundles and Policies |
    > 1236 | Bundle Information | Web
    > Intelligence Document | Bundles and Policies |
    > 1242 | Bundles and Policies Assigned to Devices | Web
    > Intelligence Document | Bundles and Policies |
    > 1239 | Content by Bundles and Policies | Web
    > Intelligence Document | Bundles and Policies |
    > 1241 | Content by Server | Web
    > Intelligence Document | Bundles and Policies |
    > 1237 | Policy Enforcement Details - Devices | Web
    > Intelligence Document | Bundles and Policies |
    > 1240 | Policy Enforcement Status | Web
    > Intelligence Document | Bundles and Policies |
    > 1164 | CISCO Routers | Web
    > Intelligence Document | Discovered Devices |
    > 1158 | Deployable Devices | Web
    > Intelligence Document | Discovered Devices |
    > 1161 | Managed Devices by ZENworks Management Zone | Web
    > Intelligence Document | Discovered Devices |
    > 1162 | Printed Page Count by Printer | Web
    > Intelligence Document | Discovered Devices |
    > 1160 | Printer Alerts | Web
    > Intelligence Document | Discovered Devices |
    > 1165 | Printer Supply Levels | Web
    > Intelligence Document | Discovered Devices |
    > 1163 | Unmanaged Servers | Web
    > Intelligence Document | Discovered Devices |
    > 1159 | Unmanaged Workstations | Web
    > Intelligence Document | Discovered Devices |
    > 1168 | Policy Assignments by Device | Web
    > Intelligence Document | EndPoint Security |
    > 1167 | Policy Assignments by User | Web
    > Intelligence Document | EndPoint Security |
    > 1181 | Zone Policy Details | Web
    > Intelligence Document | EndPoint Security |
    > 1178 | Application Control Policy Details | Web
    > Intelligence Document | Policies |
    > 1170 | Communication Hardware Policy Details | Web
    > Intelligence Document | Policies |
    > 1175 | Data Encryption Policy Details | Web
    > Intelligence Document | Policies |
    > 1179 | Firewall Policy Details | Web
    > Intelligence Document | Policies |
    > 1176 | Location Assignment Policies | Web
    > Intelligence Document | Policies |
    > 1180 | Scripting Policy Details | Web
    > Intelligence Document | Policies |
    > 1174 | Security Settings Policy Details | Web
    > Intelligence Document | Policies |
    > 1171 | Storage Device Policy Details | Web
    > Intelligence Document | Policies |
    > 1173 | USB Policy Details | Web
    > Intelligence Document | Policies |
    > 1172 | VPN enforcement Policy Details | Web
    > Intelligence Document | Policies |
    > 1177 | Wi-Fi Policy Details | Web
    > Intelligence Document | Policies |
    > 1222 | Baseline Report | Web
    > Intelligence Document | Patch Management |
    > 1221 | Bundle Deployment Summary | Web
    > Intelligence Document | Patch Management |
    > 1228 | Critical Patch Status Report | Web
    > Intelligence Document | Patch Management |
    > 1219 | Device Patch Status By Vendor | Web
    > Intelligence Document | Patch Management |
    > 1229 | Mandatory Baseline By Patch | Web
    > Intelligence Document | Patch Management |
    > 1224 | Mandatory Baseline Details | Web
    > Intelligence Document | Patch Management |
    > 1220 | Mandatory Baseline Summary | Web
    > Intelligence Document | Patch Management |
    > 1223 | Patch Analysis | Web
    > Intelligence Document | Patch Management |
    > 1227 | Patch Assesment Report | Web
    > Intelligence Document | Patch Management |
    > 1231 | Patch Bundle Deployment Status | Web
    > Intelligence Document | Patch Management |
    > 1218 | Patch Deployment Summary | Web
    > Intelligence Document | Patch Management |
    > 1232 | Patch Detail Report | Web
    > Intelligence Document | Patch Management |
    > 1226 | Patch Release Report | Web
    > Intelligence Document | Patch Management |
    > 1230 | Patch Tuesday Summary | Web
    > Intelligence Document | Patch Management |
    > 1225 | Top 10 Not Patched Critical Patches | Web
    > Intelligence Document | Patch Management |
    > 1156 | User Details Report | Web
    > Intelligence Document | User Reports |
    > 1153 | A4-Landscape | Web
    > Intelligence Document | ZENworks Standard Templates |
    > 1154 | A4-Portrait | Web
    > Intelligence Document | ZENworks Standard Templates |
    > 1152 | Letter-Landscape | Web
    > Intelligence Document | ZENworks Standard Templates |
    > 1151 | Letter-Portrait | Web
    > Intelligence Document | ZENworks Standard Templates |
    > 1204 | Device Listing | Web
    > Intelligence Document | ZENworks System |
    > 1216 | Linux Subscription Session Details | Web
    > Intelligence Document | ZENworks System |
    > 1213 | Linux Subscriptions | Web
    > Intelligence Document | ZENworks System |
    > 1207 | Managed Devices System Update Status - Windows | Web
    > Intelligence Document | ZENworks System |
    > 1214 | Non-Compliant Devices | Web
    > Intelligence Document | ZENworks System |
    > 1211 | Out of Band Power Management | Web
    > Intelligence Document | ZENworks System |
    > 1205 | Windows 7 System Readiness Report | Web
    > Intelligence Document | ZENworks System |
    > 1206 | ZENworks License Information | Web
    > Intelligence Document | ZENworks System |
    > 1215 | ZENworks Messages | Web
    > Intelligence Document | ZENworks System |
    > 1212 | ZENworks Server Statistics | Web
    > Intelligence Document | ZENworks System |
    > 1210 | Device AC power Policy | Web
    > Intelligence Document | Power Management |
    > 1209 | Power Compliance Report | Web
    > Intelligence Document | Power Management |
    > ----------------------------------------------------------------------
    > -------------------------------------------------------------------
    >
    > Is there any way to drive a report in a non-ZRS zcm setup via command
    > line without installing ZRS ?
    I think you're right. That should be mentioned in the docs. This is
    just a regular report which can be created an ran without the ZRS
    installed - so one should think you could call this command and export
    it to a file...
    Niels
    A true red devil...

  • ZPM: Need help understanding the quirks of ZPM

    Does anyone have a successful implementation of ZPM in ZCM 10.3.3 running smoothly. I have been struggling with this product since December 2010, and need a little guidance around all of the quirkiness that exists.
    So far I have found these elements that are inconsistent:
    1. Mandatory Baselines with alot of patches to apply will spawn remediate.exe sessions in parallel. There is a hard breakpoint to only allow 4 simultaneous sessions, however sometimes, the patches don't apply at all.
    2. When applying patches Windows Installer 4.5 and/or MS07 - 69, I watch it try to apply all 9 versions of the various types of patch, however the patch never successfully installs. Very strange. I assume this behavior could exist among other random patches. The patch client does not report back to the server that it failed. However, it orders the reboot to occur.
    3. There is a strange coorelation between the analyze.exe and the remediate.exe if they are running together. Sometimes, the remediate.exe will spawn chaotically if the analyze.exe is processing as well. This occurs if a load block of patches are lined up for deployment.
    4. The Graphs in the Patch Management system don't make any sense. I have 522 devices, and only 40 devices are reported on?
    My main concern is that I do not have a guaranteed process in place that will ensure patch success. I need the following things to occur:
    1. If a patch is successful, I need the server to know that it is successful. :)
    2. If the patch fails, I need to see that it fails, I need the debug mechanism in the zmd-messages log to explain why it failed, so that it can be remedied.
    3. I would like someday that the mandatory baseline feature works properly, and doesn't go crazy with spawning issues, because low-memory machines freeze up from all the memory allocations that occur.
    If anyone is out there who successfully uses this product, please let me know, because I need to steering guidance, because the controls are not obvious on how to work them, and I would hate to abandon ship, if there are some good smart workarounds that are known.
    HELP! :)

    splittgerb,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

  • Patch Bundle Deploy Remediation settings

    Got ZPM up and running and seems to be working OK on a test machine, just got a few quick qu's on behaviours when deploying updates:
    If I select a group of patches and want to use this as a baseline for all my machines am I best in using
    a) a static group \ folder
    b) applicable devices
    I don't really like the idea of "All non-patched" as it gives me no control over what goes on so leaving that out as an option. I've noticed if I do "applicable devices" the Bundle filters out some of the patches (ones it knows are already on the machine?) but if I do a Folder \ Group every patch is listed as an Install action. Chances are I need to use option a) to be sure I'm catching every machine so will ZPM just skip updates in the Install phase if they're on the machine already?
    Also when setting the Mandatory Baseline settings what I want to achieve is to allow the user to have full control over the reboot process i.e. they can reboot now, reboot later (snooze) or not reboot at all so my first guess on the settings was this:
    Suppress Reboot: YES
    Allow User to cancel: YES
    Time to show dialog before reboot: 120
    Allow User to snooze: YES
    When deploying some patches I saw a box slide out from the system tray but it disappeared before I could do anything with it (hence setting the above to 120 seconds). Question is do any of the options override each other e.g. if I set the dialog to 120 will that auto reboot even though I've allowed user to suppress it?

    I am also interested in the best process to accomplish patch deployment. I have noticed that some patches tend to fail due to a variety of issues. Once the patch has been deployed whether it fails or not it is considered deployed and a Verify or redeployment of the patch is required to patch things up.
    As far as a baseline setup this will provide several options that from my understanding are unrelated to each other. ie a "Snooze" setting of 120 seconds is not the same as a force reboot setting. This setup also doesn't seem to have any effect for the settings that are used for Patch deployment outside of the baseline setup. So if you deploy to a group or set of devices the settings listed in the baseline settings do not hold true to the patch bundles settings.
    I too like the idea of baseline setup for specific dynamic groups and have played with them on specific groups. I haven't seen any major issues but have also heard the horror stories and remarks not to use baselines in this way.
    Here is what I have done so far. I assign the patch bundles by month to the dynamic group (ie Windows 7). The end user notify settings are setup so that I add my departments information to the reboot notice that scrolls up near the system tray. I setup a allow user to snooze for the 120 seconds and force a reboot after 10 hours. This gives my end user a full days work before the device must be rebooted. Only complaint I have had from my end users is that the pop-up seems to be to persistent and they had wished for a far less notification time say once every few hours.
    I am looking for a better way to deploy patch's then I currently have. I would like to have patch's deploy out if they have failed before. I always looked at the baseline as that way but with Novell documentation stating not to do this I have moved away from this deployment type. I would like to have Critical MS patch's deploy out and have a way to verify that the patch is deployed and if not redeploy automatically.
    The largest issue I have with patch deployment is that the large part of my deployment are student computers. So if the patch process in place takes longer then a half hour then the chance is extremely great that the laptop will either be place in sleep/hibernation mode or shutdown completely. Keeping the patch bundles to a small deployment seems to be the best way to go but I have had major issues with Patch deployment showing a successful deployment only to have the patch's for that device to show a non-patched. From what I can see from another post this is a known issue with a workaround.
    Richard

  • Is BaseLining mandatory for Tracking Gantt in Project Server ?

    Hello all,
    I am new to Project Sever and I am feeling a bit uncomfortable with the usage of baselines. I just want a simple implementation where I will have my own custom defined Actual Task Start and Actual Task Finish to track the tasks. But is it possible to have
    a Tracking gantt chart using these custom fields in PWA ?
    I found no OOTB options to set the dates to be looked for tracking in the gantt customization.
    Please update me with this. If there is no other way, then I will go ahead with the Baselines.
    Thanks,
    Shanky

    Hello Guillaume Rouyre,
    The requirement in my case is that the engineers are allowed to enter tasks at a later point of stage in the project lifecycle.
    ie., Say the Engineer creates 2 tasks with    
    T1 & T2   :   Start: 1/2/2015      and   Finish 28/2/2015
    Now the manger saves the "Baseline"
    Now say the engineer updates these tasks with actuals as     
    T1 & T2  :  Start: 5/2/205        and            Finish: 5/3/2015
    Now the manager can see the Tracking gantt, the difference between the planned and actuals on the gantt chart.
    But say, at this point of time the engineer adds 2 more tasks with say date    
    T3 & T4 : Start: 5/3/2015    and Finish: 30/3/2015.
    Now these 2 tasks are not saved in "Baseline", hence the manager wont be able to track these tasks on the gantt chart. For this the manager has to set another baseline, "Baseline1" and if the engineer changes the dates for the last 2
    tasks there after, the manager is unable to track these 2 tasks in the Tracking gantt chart, as the tracking gantt chart shows just the difference with the "Baseline" dates (But these 2 last added tasks are not a part of the Baseline, but are a part
    of Baseline1). Until and unless I save all the tasks into a single baseline, I am unable to view all the tasks on the tracking gantt chart in Tracking View.
    When I checked in the forums, I saw something about Interim Plan, where the manager can save temporarily these baselines and then combine it. But to my surprise I am unable to find that "Interim Plan" in Project Server 2013 PWA. 
    So is there a way that, the manager must be able to track all the tasks added by the engineer at any point of time in the project lifecycle through the "Tracking gantt charts" ? 

  • MIRO baseline date

    hi all,
    please help me to solve this issue
    issue:
    MIRO baseline date getting defaulted and hence leading to wrong calculation of payment terms. Payment date to be made mandatory and no default baseline date
    atanu

    Hi Atanu,
    Base line date will be used for clearing payments in FI.
    Base line date can be defaulted based on your payment terms too i.e.
    (a) No Default
    (b) Based on your posting date
    (c) Based on your document date
    (d) Based on you Entry date.
    Hope this informaion will be useful
    Bye,
    Muralidhara

  • Baseline Date for Due Date Calculation required for S/L indicators

    Hello,
    Iu2019m facing the following problem
    Iu2019m trying to insert an invoice (using a customer master record) but the system blocks me because the field ZFBDT (Baseline Date for Due Date Calculation) is a Required entry.
    The strange thing is  that if I use a S/L indicators the field is mandatory, if not the date may be defaulted.
    I checked in OB41 but there are non differences between Special PK and normal PK.
    Any ideas?
    Thanks in advance
    Alberto

    Dear Alberto,
    the field "Due On (BSEG-ZFBDT)" cannot be controlled with field status.
    It is controlled by field attribute of screen painter (Tcd: SE51).  If
    you look at element attribute for "Due On" field, a flag for required
    entry is activated.  In this case, field status has no control over
    the field.
    As of release 3.1G, field BSEG-ZFBDT is hardcoded in most FI screens
    to be mandatory and cannot be influenced by any field status
    changes. This situation is only valid when posting with special G/L
    indicator (ie PK 29/39).
    SAP development team has determined that this is a critical field.  The
    reason behind this is that this special GL screen and the data entered
    here are very important to many other programs. This data affects
    liabilities and receivables where due date is necessary almost
    everytime. Thus, we changed this field in this screen in order to
    prevent problems in many other areas. The reason is explained further
    in note 95079.
    I hope this helps You.
    mauri

  • Need to crawl a graphic and make it dissapear

    Here is a little poser I stumbled on...and I wonder how others would do this in PPRO (CS5).
    I have a base line title created in PPRO Titler  ( "a string of six words capatilised")
    I need to make them crawl right to left across the baseline and then dissapear  at the leading edge part way across  (just preceding a logo about 8/10ths across the screen.)
    Ideally ...dissapear behind a slightly feathered edge.
    How would you do this?
    BTW: I have done it in AEFX but was surprised that I stumbled on this simple thing in PPRO.

    Thanx Guys.
    I will try your suggestions and I am very familiar with the Linear Wipe.  I use it for
    graphic line reveals a lot.
    I did play with it a bit yesterday along with Track Mattes and Garbage Mattes.
    Will have another play now. (not totally convinced I will add)
    It was real easy to do in AEFX but I am taken aback by how hard it is to do in PPRO.
    I am persevering for my own edification at his point and I do have a few of them to do for this project and upcoming ones.

  • Making a text field mandatory if another text field is populated

    Hi all,
    I had this question at the bottom of another thread which might have been missed. Apologies if I've broken forum rules by starting a new thread...
    Question is about Acrobat X Professional form's
    I have fields called Milestone and Baseline which are both text boxes, initially empty when the form opens and default to non-mandatory.
    When someone enters something in the Milestone box I want to ensure that they have to complete a Baseline date.
    Thanks in advance

    Hi George
    I put your code into the Java box on the Milestone but it never quite did the trick..
    Do the images below help ?

  • Restricting submission to the baseline to a subset of Planners

    Planners need to be able to create, delete, and update scenarios.
    However, only one group of those planners should have the ability to submit a scenario to the baseline.
    Is there a way to restrict the ability to submit to the baseline to only a subset of the Planners? Even then, we would like to restrict the changes to a subset of measures when those can be submitted to the baseline.
    An example of how to do this in IOP 11.2 would be most helpful.
    Thank you.

    I believe so. If all the groups which need scenario creation ability, but should not have submit capability, are assigned a mandatory approver, it becomes a business process for that approver to not approve the submission to the baseline. Not setting up a mandatory approver for the group that can actually submit data to the baseline should be simple enough.
    Restricting data update through security filters is something I already have experience with.
    Restricting access to who can see a particular subset of the data is more complicated, as security filters control what you can update, but not what you can see within the application.
    Thank you.

  • What are the mandatory fields while creation of material master in differen

    what are the mandatory fields while creation of material master in different views?

    Hi Gopi,
      This is purely depends on the function configuration, which would be done MM consultants.  Kindly check with them.
    thanks & regards
    Kishore Kumar Maram

  • Dynamic mandatory field error message is not getting displayed in webui

    Hi,
    In Appointment if the importance is HIGH i made Location as mandatory.For this i enhanced BT126H_APPT/ApptDetails. In the get_p_location() method of BTACTIVITYYH i have written the code.
    Now the problem is Error message for this dynamic mandatory field is not getting displayed in webui.
    I debugged in DO_FINISH_INPUT error message is getting generated but it is not getting displayed in ui.
    Can anybody tell where the problem is?
    Thanks,
    Hari.

    Hi Hari,
    Really sorry do not know how to convert this nug file to text
    How ever quick solution for your problem would be just keep your validation in 'DO_VALIDATE_INPUT' method of the view controller.
    Means even if the User clicks on SAVE , Since it fails here , it would not allow you to go further.
    Thanks,
    Rajesh P

Maybe you are looking for